{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-58026 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-58026 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-58026 is a medium-severity cross-site scripting vulnerability in Termageddon: Cookie Consent \u0026 Privacy Compliance, published on 22 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-58026 and fix it if it is affected.\n\nWhat it is: CVE-2025-58026 is a medium-severity cross-site scripting vulnerability in Termageddon: Cookie Consent \u0026 Privacy Compliance, published on 22 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-58026 in the wild and no public exploit code.\n\nAffected product: Termageddon: Cookie Consent \u0026 Privacy Compliance. 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-58026/ (Markdown: https://insights.sbomify.com/CVE-2025-58026/index.md)","id":"CVE-2025-58026","markdown":"https://insights.sbomify.com/CVE-2025-58026/index.md","name":"CVE-2025-58026","record":{"aliases":["GHSA-6c42-q364-455m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Stored XSS in Termageddon WordPress plugin allows attackers to inject malicious scripts, potentially leading to session hijacking or site defacement.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in termageddon Termageddon: Cookie Consent \u0026 Privacy Compliance termageddon-usercentrics allows Stored XSS.This issue affects Termageddon: Cookie Consent \u0026 Privacy Compliance: from n/a through \u003c= 1.8.1.","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":"WordPress Termageddon: Cookie Consent \u0026 Privacy Compliance Plugin \u003c= 1.8.1 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-58026","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress NGG Smart Image Search Plugin \u003c= 3.4.3 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-58027"},"packages":[],"prev":{"headline":"WordPress Master Slider Plugin \u003c= 3.11.0 - Cross Site Scripting (XSS) Vulnerability","id":"CVE-2025-58025"},"products":["Termageddon: Cookie Consent \u0026 Privacy Compliance"],"published":"2025-09-22","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["termageddon"]},"summary":"Stored XSS in Termageddon WordPress plugin allows attackers to inject malicious scripts, potentially leading to session hijacking or site defacement.","url":"https://insights.sbomify.com/CVE-2025-58026/"}