{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-13419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-13419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-13419 is a medium-severity missing authorization vulnerability in aharonyan Guest posting / Frontend Posting / Front Editor – WP Front User Submit, published on 7 Jan 2026. 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-13419 and fix it if it is affected.\n\nWhat it is: CVE-2025-13419 is a medium-severity missing authorization vulnerability in aharonyan Guest posting / Frontend Posting / Front Editor – WP Front User Submit, published on 7 Jan 2026. 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-13419 in the wild and no public exploit code.\n\nAffected product: aharonyan Guest posting / Frontend Posting / Front Editor – WP Front User Submit. 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-13419/ (Markdown: https://insights.sbomify.com/CVE-2025-13419/index.md)","id":"CVE-2025-13419","markdown":"https://insights.sbomify.com/CVE-2025-13419/index.md","name":"CVE-2025-13419","record":{"aliases":["GHSA-8jxh-xpcf-824x"],"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":"Unauthenticated attackers can delete arbitrary media attachments due to a missing capability check in the WP Front User Submit plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Guest posting / Frontend Posting / Front Editor – WP Front User Submit plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the '/wp-json/bfe/v1/revert' REST API endpoint in all versions up to, and including, 5.0.0. This makes it possible for unauthenticated attackers to delete arbitrary media attachments.","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":"Missing authorization in Guest posting / Frontend Posting / Front Editor – WP Front User Submit","id":"CVE-2025-13419","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":"itsourcecode Human Resource Management System EventStore.php sql injection","id":"CVE-2025-13420"},"packages":[],"prev":{"headline":"Responsive Pricing Table \u003c= 5.1.12 - Authenticated (Author+) Stored Cross-Site Scripting","id":"CVE-2025-13418"},"products":["Guest posting / Frontend Posting / Front Editor – WP Front User Submit"],"published":"2026-01-07","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":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["aharonyan"]},"summary":"Unauthenticated attackers can delete arbitrary media attachments due to a missing capability check in the WP Front User Submit plugin.","url":"https://insights.sbomify.com/CVE-2025-13419/"}