{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-104006 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-104006 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104006 is a low-severity vulnerability in softaculous SpeedyCache – Cache, Optimization, Performance, published on 10 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-104006 and fix it if it is affected.\n\nWhat it is: CVE-2026-104006 is a low-severity vulnerability in softaculous SpeedyCache – Cache, Optimization, Performance, published on 10 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-104006 in the wild and no public exploit code.\n\nAffected product: softaculous SpeedyCache – Cache, Optimization, Performance. 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-104006/ (Markdown: https://insights.sbomify.com/CVE-2026-104006/index.md)","id":"CVE-2026-104006","markdown":"https://insights.sbomify.com/CVE-2026-104006/index.md","name":"CVE-2026-104006","record":{"aliases":["GHSA-fvr3-4rq4-9pc2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress caching plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract returning commenters' names and emails from cached pages due to missing cookie checks on the cache write path.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"description":"The SpeedyCache – Cache, Optimization, Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.2 via the 'comment_author_*, comment_author_email_*' parameter. This makes it possible for unauthenticated attackers to extract the full name and email address of returning commenters pre-filled into comment form input fields and persisted as the site-wide cached page by any unauthenticated attacker requesting the same public URL. The read-side handler in advanced-cache.php correctly skips cached delivery for requests carrying comment_author_* cookies, but this check is absent on the write path, meaning the cache poisoning is invisible to the victim commenter yet fully exploitable by any unauthenticated attacker with no cookies.","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":"Information disclosure in SpeedyCache – Cache, Optimization, Performance","id":"CVE-2026-104006","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) \u003c= _inputEnd and then, on the fast path","id":"CVE-2026-104016"},"packages":[],"prev":{"headline":"Incorrect authorization in MongoDB Server router for bulk writes to system namespaces","id":"CVE-2026-104005"},"products":["SpeedyCache – Cache, Optimization, Performance"],"published":"2026-10-10","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-10-11","vendors":["softaculous"]},"summary":"Unauthenticated attackers can extract returning commenters' names and emails from cached pages due to missing cookie checks on the cache write path.","url":"https://insights.sbomify.com/CVE-2026-104006/"}