{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38669 exists.","fix":"No fix has been published for CVE-2026-38669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-38669 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 May 2026. 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-2026-38669 and fix it if it is affected.\n\nWhat it is: CVE-2026-38669 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 May 2026. 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-2026-38669 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-2026-38669/ (Markdown: https://insights.sbomify.com/CVE-2026-38669/index.md)","id":"CVE-2026-38669","markdown":"https://insights.sbomify.com/CVE-2026-38669/index.md","name":"CVE-2026-38669","record":{"aliases":["GHSA-3qqq-w8vx-5mw3"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"wCMS","requires_auth":"none","summary":"Attackers can inject malicious scripts via blog creation in wCMS, potentially stealing user data or executing code.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"wCMS v.1.4 is vulnerable to Cross Site Scripting (XSS) when creating a new blog.","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":"Cross-site scripting in n/a","id":"CVE-2026-38669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-38671"},"packages":[],"prev":{"headline":"Netmaker does not verify JWT signatures for host tokens","id":"CVE-2026-38651"},"products":["n/a"],"published":"2026-05-04","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-05-04","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts via blog creation in wCMS, potentially stealing user data or executing code.","url":"https://insights.sbomify.com/CVE-2026-38669/"}