{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-79713 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-79713 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-79713 is a medium-severity vulnerability in Unknown Breeze Cache, published on 18 Sep 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-79713 and fix it if it is affected.\n\nWhat it is: CVE-2026-79713 is a medium-severity vulnerability in Unknown Breeze Cache, published on 18 Sep 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-79713 in the wild and no public exploit code.\n\nAffected product: Unknown Breeze Cache. 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-79713/ (Markdown: https://insights.sbomify.com/CVE-2026-79713/index.md)","id":"CVE-2026-79713","markdown":"https://insights.sbomify.com/CVE-2026-79713/index.md","name":"CVE-2026-79713","record":{"aliases":["GHSA-7m74-3h9w-8cpx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress caching plugin","requires_auth":"none","summary":"Unauthenticated attackers can poison the page cache by omitting tracking parameters from the cache key, serving malicious content to all visitors.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","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-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"The Breeze Cache WordPress plugin before 2.5.15 does not include a set of tracking-related query parameters in its page-cache key while still caching pages requested with them, allowing unauthenticated attackers to have a page rendered under their own request context stored under, and served from, the clean URL's cache entry to every subsequent visitor.","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":"Breeze Cache 1.2.5 - 2.5.14 - Unauthenticated Cache Poisoning via Unkeyed Tracking Parameters","id":"CVE-2026-79713","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"IBM WebSphere Application Server Liberty Path Traversal","id":"CVE-2026-79715"},"packages":[],"prev":{"headline":"Incorrect Authorization in GitLab","id":"CVE-2026-79708"},"products":["Breeze Cache"],"published":"2026-09-18","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-09-18","vendors":["Unknown"]},"summary":"Unauthenticated attackers can poison the page cache by omitting tracking parameters from the cache key, serving malicious content to all visitors.","url":"https://insights.sbomify.com/CVE-2026-79713/"}