CVE-2025-31729: WordPress WooTumblog plugin <= 2.1.4 - Content Injection vulnerability
First published: Thu Apr 03 2025(Updated: )
Missing Authorization vulnerability in jeffikus WooTumblog allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WooTumblog: from n/a through 2.1.4.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress WooTumblog | <=2.1.4 | |
| WooTumblog | <=2.1.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-31729?
The severity of CVE-2025-31729 is considered medium due to the risk of unauthorized access through misconfigured security levels.
How do I fix CVE-2025-31729?
To fix CVE-2025-31729, you should update the WooTumblog plugin to version 2.1.5 or later, ensuring proper access control settings.
What are the potential risks associated with CVE-2025-31729?
The risks associated with CVE-2025-31729 include unauthorized access to sensitive data and potential exploitation of administrative functions.
Which versions of WooTumblog are affected by CVE-2025-31729?
CVE-2025-31729 affects versions of WooTumblog from n/a up to and including 2.1.4.
Who is the vendor responsible for CVE-2025-31729?
The vendor responsible for CVE-2025-31729 is Jeffikus, the creator of the WooTumblog plugin.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/weakness
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/severity
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/epss
- agent/tags
- vendor/jeffikus
- canonical/wordpress wootumblog
- vendor/wordpress
- canonical/wootumblog