{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-91830 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-91830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91830 is a medium-severity vulnerability in Unknown Subscribe to Comments, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-91830 and fix it if it is affected.\n\nWhat it is: CVE-2026-91830 is a medium-severity vulnerability in Unknown Subscribe to Comments, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-91830 in the wild and no public exploit code.\n\nAffected product: Unknown Subscribe to Comments. 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-91830/ (Markdown: https://insights.sbomify.com/CVE-2026-91830/index.md)","id":"CVE-2026-91830","markdown":"https://insights.sbomify.com/CVE-2026-91830/index.md","name":"CVE-2026-91830","record":{"aliases":["GHSA-vg8j-9jxp-q7qm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can disclose subscriber management keys via forged cookies, allowing them to read and modify user subscriptions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Subscribe to Comments WordPress plugin before 2.3.3 does not sign or validate a cookie it trusts to identify a commenter, allowing unauthenticated attackers to disclose a subscriber's management key and silently alter that subscriber's subscriptions.","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":"Subscribe to Comments \u003c 2.3.3 - Unauthenticated Subscription Management Key Disclosure via Forged Comment Cookie","id":"CVE-2026-91830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Subscribe to Comments 2.3 - 2.3.2 - Author+ Email Header Injection via From Name Setting","id":"CVE-2026-91831"},"packages":[],"prev":{"headline":"Subscribe to Comments \u003c 2.3.3 - Reflected XSS via 'ref' Parameter","id":"CVE-2026-91829"},"products":["Subscribe to Comments"],"published":"2026-10-16","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Unknown"]},"summary":"Unauthenticated attackers can disclose subscriber management keys via forged cookies, allowing them to read and modify user subscriptions.","url":"https://insights.sbomify.com/CVE-2026-91830/"}