{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-31729 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-31729 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-31729 is a medium-severity missing authorization vulnerability in jeffikus WooTumblog, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-31729 and fix it if it is affected.\n\nWhat it is: CVE-2025-31729 is a medium-severity missing authorization vulnerability in jeffikus WooTumblog, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-31729 in the wild and no public exploit code.\n\nAffected product: jeffikus WooTumblog. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-31729/ (Markdown: https://insights.sbomify.com/CVE-2025-31729/index.md)","id":"CVE-2025-31729","markdown":"https://insights.sbomify.com/CVE-2025-31729/index.md","name":"CVE-2025-31729","record":{"aliases":["GHSA-4h89-j5fq-8vxv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject content into WooTumblog posts due to missing authorization checks, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing Authorization vulnerability in jeffikus WooTumblog woo-tumblog allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooTumblog: from n/a through \u003c= 2.1.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress WooTumblog plugin \u003c= 2.1.4 - Content Injection vulnerability","id":"CVE-2025-31729","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Marketer Addons Plugin \u003c= 1.0.1 - Stored Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-31730"},"packages":[],"prev":{"headline":"Jenkins AsakusaSatellite Plugin Does not Mask API Keys via Job Configuration Form","id":"CVE-2025-31728"},"products":["WooTumblog"],"published":"2025-04-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["jeffikus"]},"summary":"Attackers can inject content into WooTumblog posts due to missing authorization checks, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2025-31729/"}