{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-28908 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-28908 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-28908 is a medium-severity cross-site scripting vulnerability in pipdig pipDisqus, published on 11 Mar 2025. 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-2025-28908 and fix it if it is affected.\n\nWhat it is: CVE-2025-28908 is a medium-severity cross-site scripting vulnerability in pipdig pipDisqus, published on 11 Mar 2025. 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-2025-28908 in the wild and no public exploit code.\n\nAffected product: pipdig pipDisqus. 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-28908/ (Markdown: https://insights.sbomify.com/CVE-2025-28908/index.md)","id":"CVE-2025-28908","markdown":"https://insights.sbomify.com/CVE-2025-28908/index.md","name":"CVE-2025-28908","record":{"aliases":["GHSA-9g29-43mh-wwf6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Stored XSS in pipDisqus allows attackers to inject malicious scripts into WordPress sites, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 pipdig pipDisqus pipdisqus allows Stored XSS.This issue affects pipDisqus: from n/a through \u003c= 1.6.","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 pipDisqus plugin \u003c= 1.6 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-28908","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 WP No-Bot Question plugin \u003c= 0.1.7 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2025-28909"},"packages":[],"prev":{"headline":"WordPress WP Last Modified plugin \u003c= 0.1 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-28907"},"products":["pipDisqus"],"published":"2025-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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["pipdig"]},"summary":"Stored XSS in pipDisqus allows attackers to inject malicious scripts into WordPress sites, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2025-28908/"}