{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4409 is a medium-severity missing authorization vulnerability in wpkube Subscribe To Comments Reloaded, published on 5 May 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-4409 and fix it if it is affected.\n\nWhat it is: CVE-2026-4409 is a medium-severity missing authorization vulnerability in wpkube Subscribe To Comments Reloaded, published on 5 May 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-4409 in the wild and no public exploit code.\n\nAffected product: wpkube Subscribe To Comments Reloaded. 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-4409/ (Markdown: https://insights.sbomify.com/CVE-2026-4409/index.md)","id":"CVE-2026-4409","markdown":"https://insights.sbomify.com/CVE-2026-4409/index.md","name":"CVE-2026-4409","record":{"aliases":["GHSA-gwh7-h25p-fjxv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can forge authorization keys to manage comment subscription preferences for arbitrary users due to leaked secrets and weak hashing.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","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 Reloaded plugin for WordPress is vulnerable to unauthorized modification of data due to a leaked secret key and usage of a weak hash generation algorithm in all versions up to, and including, 240119. This makes it possible for unauthenticated attackers to extract the global key from any public post page, forge authorization keys and manage comment subscription preferences for arbitrary users","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 Reloaded \u003c= 240119 - Improper Authorization to Unauthenticated Arbitrary Subscription Management","id":"CVE-2026-4409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by a denial of service","id":"CVE-2026-4410"},"packages":[],"prev":{"headline":"Samba: remote code execution in samr","id":"CVE-2026-4408"},"products":["Subscribe To Comments Reloaded"],"published":"2026-05-05","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-05-05","vendors":["wpkube"]},"summary":"Unauthenticated attackers can forge authorization keys to manage comment subscription preferences for arbitrary users due to leaked secrets and weak hashing.","url":"https://insights.sbomify.com/CVE-2026-4409/"}