{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92424 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92424 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92424 is a medium-severity cross-site scripting vulnerability in Unknown Content Egg, published on 30 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-92424 and fix it if it is affected.\n\nWhat it is: CVE-2026-92424 is a medium-severity cross-site scripting vulnerability in Unknown Content Egg, published on 30 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-92424 in the wild and no public exploit code.\n\nAffected product: Unknown Content Egg. 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-92424/ (Markdown: https://insights.sbomify.com/CVE-2026-92424/index.md)","id":"CVE-2026-92424","markdown":"https://insights.sbomify.com/CVE-2026-92424/index.md","name":"CVE-2026-92424","record":{"aliases":["GHSA-f6mm-vhgg-jr4m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Contributors can inject stored XSS via the import queue, executing scripts in the context of privileged users viewing the content.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Content Egg  WordPress plugin before 11.9.0 does not verify that a user running its bulk content-import feature is authorized for the import preset they select, and switches to the preset author's identity before creating the resulting post, allowing users with contributor-level access and above to store arbitrary web scripts unfiltered under a privileged user's account, executing in the context of anyone who later views that content.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-29T19:06:54Z","kind":"github_poc","ref":"https://github.com/aymencdm/cve-2026-92424-content-egg-stored-xss-","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Content Egg \u003c 11.9.0 - Contributor+ Stored XSS via Import Queue","id":"CVE-2026-92424","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Hydra Booking \u003c 1.2.4 - Hydra Host+ Cross-Host Account Modification and Deletion via IDOR","id":"CVE-2026-92425"},"packages":[],"prev":{"headline":"Meow Gallery \u003c 5.5.5 - Author+ Draft and Private Post Disclosure via fetch_posts","id":"CVE-2026-92423"},"products":["Content Egg"],"published":"2026-09-30","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Unknown"]},"summary":"Contributors can inject stored XSS via the import queue, executing scripts in the context of privileged users viewing the content.","url":"https://insights.sbomify.com/CVE-2026-92424/"}