{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11869 exists.","fix":"No fix has been published for CVE-2019-11869 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11869 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-11869 and fix it if it is affected.\n\nWhat it is: CVE-2019-11869 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11869 exists.\n\nAffected product: n/a. 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-2019-11869/ (Markdown: https://insights.sbomify.com/CVE-2019-11869/index.md)","id":"CVE-2019-11869","markdown":"https://insights.sbomify.com/CVE-2019-11869/index.md","name":"CVE-2019-11869","record":{"aliases":["GHSA-j5p6-8vxr-w5gp"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An unauthenticated attacker can inject malicious scripts into the Yuzo Related Posts plugin settings due to flawed admin verification logic.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yuzo","vendor":"yuzopro"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Yuzo Related Posts plugin 5.12.94 for WordPress has XSS because it mistakenly expects that is_admin() verifies that the request comes from an admin user (it actually only verifies that the request is for an admin page). An unauthenticated attacker can inject a payload into the plugin settings, such as the yuzo_related_post_css_and_style setting.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-11-14","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2024-11-14T00:57:57Z","kind":"github_poc","ref":"https://github.com/gitrecon1455/CVE-2019-11869","stars":0,"title":null},{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-11869.yaml","stars":null,"title":"WordPress Yuzo \u003c5.12.94 - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2019-11869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-11870"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-11868"},"products":["n/a"],"published":"2019-05-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An unauthenticated attacker can inject malicious scripts into the Yuzo Related Posts plugin settings due to flawed admin verification logic.","url":"https://insights.sbomify.com/CVE-2019-11869/"}