{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6275 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6275 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6275 is a medium-severity cross-site scripting vulnerability in StatCounter – Free Real Time Visitor Stats, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6275 and fix it if it is affected.\n\nWhat it is: CVE-2026-6275 is a medium-severity cross-site scripting vulnerability in StatCounter – Free Real Time Visitor Stats, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6275 in the wild and no public exploit code.\n\nAffected product: StatCounter – Free Real Time Visitor Stats. 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-6275/ (Markdown: https://insights.sbomify.com/CVE-2026-6275/index.md)","id":"CVE-2026-6275","markdown":"https://insights.sbomify.com/CVE-2026-6275/index.md","name":"CVE-2026-6275","record":{"aliases":["GHSA-fm82-44w2-4gmf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can inject arbitrary scripts via author nicknames, executing code on visitor pages in the StatCounter WordPress plugin.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The StatCounter – Free Real Time Visitor Stats plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.1.1 This is due to insufficient output escaping on the post author's nickname in the statcounter_addToTags() function. The function is hooked to wp_head and fires on every single post page. It retrieves the post author's nickname via the_author_meta() and echoes it directly into a JavaScript double-quoted string context inside a \u003cscript\u003e block without applying esc_js() or any equivalent JavaScript-context escaping. This makes it possible for authenticated attackers with Author-level access and above to inject arbitrary web scripts into pages that will execute whenever any user (including unauthenticated visitors) accesses a post authored by the attacker.","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":"StatCounter \u003c= 2.1.1 - Authenticated (Author+) Stored Cross-Site Scripting via Author Nickname","id":"CVE-2026-6275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"stale custom cookie host causes cookie leak","id":"CVE-2026-6276"},"packages":[],"prev":{"headline":"Authentication Bypass in DTS Electronics' Redline WR3200","id":"CVE-2026-6274"},"products":["StatCounter – Free Real Time Visitor Stats"],"published":"2026-05-29","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-05-29","vendors":["statcounter"]},"summary":"Authenticated attackers can inject arbitrary scripts via author nicknames, executing code on visitor pages in the StatCounter WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-6275/"}