{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-10001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-10001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-10001 is a medium-severity cross-site scripting vulnerability in Unknown WP-Stats, published on 1 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2015-10001 and fix it if it is affected.\n\nWhat it is: CVE-2015-10001 is a medium-severity cross-site scripting vulnerability in Unknown WP-Stats, published on 1 Nov 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2015-10001 in the wild and no public exploit code.\n\nAffected product: Unknown WP-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-2015-10001/ (Markdown: https://insights.sbomify.com/CVE-2015-10001/index.md)","id":"CVE-2015-10001","markdown":"https://insights.sbomify.com/CVE-2015-10001/index.md","name":"CVE-2015-10001","record":{"aliases":["GHSA-2wcw-gx74-hx8q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via CSRF in WP-Stats settings, leading to stored XSS and potential site compromise.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp-stats","vendor":"wp-stats_project"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP-Stats WordPress plugin before 2.52 does not have CSRF check when saving its settings, and did not escape some of them when outputting them, allowing attacker to make logged in high privilege users change them and set Cross-Site Scripting payloads","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":"WP-Stats \u003c 2.5.2 - CSRF to Stored Cross-Site Scripting (XSS)","id":"CVE-2015-10001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2015"},"n_packages":0,"n_references":2,"next":{"headline":"Kiddoware Kids Place Home Button Protection denial of service","id":"CVE-2015-10002"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2015-9551"},"products":["WP-Stats"],"published":"2021-11-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts via CSRF in WP-Stats settings, leading to stored XSS and potential site compromise.","url":"https://insights.sbomify.com/CVE-2015-10001/"}