{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-13149 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-13149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-13149 is a medium-severity missing authorization vulnerability in Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories, published on 21 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-13149 and fix it if it is affected.\n\nWhat it is: CVE-2025-13149 is a medium-severity missing authorization vulnerability in Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories, published on 21 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-13149 in the wild and no public exploit code.\n\nAffected product: Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories. 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-13149/ (Markdown: https://insights.sbomify.com/CVE-2025-13149/index.md)","id":"CVE-2025-13149","markdown":"https://insights.sbomify.com/CVE-2025-13149/index.md","name":"CVE-2025-13149","record":{"aliases":["GHSA-j4v2-25rp-cpm7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated authors can modify the status of arbitrary posts and pages due to missing authorization checks in the REST API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the \"saveFutureActionData\" function in all versions up to, and including, 4.9.1. This makes it possible for authenticated attackers, with author level access and above, to change the status of arbitrary posts and pages via the REST API endpoint.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories","id":"CVE-2025-13149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"CVE-2025-13151","id":"CVE-2025-13151"},"packages":[],"prev":{"headline":"IBM Aspera Orchestrator Unverified Password Change","id":"CVE-2025-13148"},"products":["Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories"],"published":"2025-11-21","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["publishpress"]},"summary":"Authenticated authors can modify the status of arbitrary posts and pages due to missing authorization checks in the REST API.","url":"https://insights.sbomify.com/CVE-2025-13149/"}