{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1867 exists.","fix":"No fix has been published for CVE-2026-1867 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1867 is a medium-severity vulnerability in Unknown Guest posting / Frontend Posting / Front Editor, published on 11 Mar 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-2026-1867 and fix it if it is affected.\n\nWhat it is: CVE-2026-1867 is a medium-severity vulnerability in Unknown Guest posting / Frontend Posting / Front Editor, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1867 exists.\n\nAffected product: Unknown Guest posting / Frontend Posting / Front Editor. 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-2026-1867/ (Markdown: https://insights.sbomify.com/CVE-2026-1867/index.md)","id":"CVE-2026-1867","markdown":"https://insights.sbomify.com/CVE-2026-1867/index.md","name":"CVE-2026-1867","record":{"aliases":["GHSA-w8vw-4787-pf8f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can expose sensitive form data and admin emails if admin notifications are enabled in the WP Front User Submit plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Guest posting / Frontend Posting / Front Editor  WordPress plugin before 5.0.6 allows passing a URL parameter to regenerate a .json file based on demo data that it initially creates. If an administrator modifies the demo form and enables admin notifications in the Guest posting / Frontend Posting / Front Editor  WordPress plugin before 5.0.6's settings, it is possible for an unauthenticated attacker to export and download all of the form data/settings, including the administrator's email address.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP Front User Submit \u003c 5.0.6 - Unauthenticated Sensitive Information Exposure","id":"CVE-2026-1867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Neutralization of Special Elements Used in a Template Engine in GitLab AI Gateway","id":"CVE-2026-1868"},"packages":[],"prev":{"headline":"Cross-site scripting in Name Directory","id":"CVE-2026-1866"},"products":["Guest posting / Frontend Posting / Front Editor"],"published":"2026-03-11","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-11","vendors":["Unknown"]},"summary":"Unauthenticated attackers can expose sensitive form data and admin emails if admin notifications are enabled in the WP Front User Submit plugin.","url":"https://insights.sbomify.com/CVE-2026-1867/"}