{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-4951 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4951 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4951 is a medium-severity cross-site scripting vulnerability in Rapid7 AppSpider Pro, published on 20 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-4951 and fix it if it is affected.\n\nWhat it is: CVE-2025-4951 is a medium-severity cross-site scripting vulnerability in Rapid7 AppSpider Pro, published on 20 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-4951 in the wild and no public exploit code.\n\nAffected product: Rapid7 AppSpider Pro. 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-2025-4951/ (Markdown: https://insights.sbomify.com/CVE-2025-4951/index.md)","id":"CVE-2025-4951","markdown":"https://insights.sbomify.com/CVE-2025-4951/index.md","name":"CVE-2025-4951","record":{"aliases":["GHSA-f252-qh43-5v8p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Rapid7 AppSpider Pro","requires_auth":"low_privilege","summary":"Stored XSS in ScanName field allows attackers to execute scripts if configuration file is modified, impacting AppSpider Pro users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"appspider_pro","vendor":"rapid7"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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":"Editions of Rapid7 AppSpider Pro before version 7.5.018 is vulnerable to a stored cross-site scripting vulnerability in the \"ScanName\" field.\nDespite the application preventing the inclusion of special characters within the \"ScanName\" field, this could be bypassed by modifying the configuration file directly.\n\nThis is fixed as of version 7.5.018","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":"Cross-site scripting in AppSpider Pro","id":"CVE-2025-4951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Denial-of-service vulnerability in ESET security products for Windows","id":"CVE-2025-4952"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-4950"},"products":["AppSpider Pro"],"published":"2025-05-20","related":[{"cvss_score":7.8,"headline":"Other in AppSpider Pro","id":"CVE-2017-5236","kev_date_added":null,"published":"2017-05-03"},{"cvss_score":7.8,"headline":"Other in AppSpider Pro","id":"CVE-2017-5233","kev_date_added":null,"published":"2017-03-02"},{"cvss_score":7.5,"headline":"Memory corruption in AppSpider Pro","id":"CVE-2017-5240","kev_date_added":null,"published":"2017-05-03"},{"cvss_score":3.3,"headline":"Rapid7 AppSpider Project Name Validation Bypass","id":"CVE-2025-11195","kev_date_added":null,"published":"2025-09-30"},{"cvss_score":3.3,"headline":"Rapid7 Appspider Broken Access Control Vulnerability","id":"CVE-2025-36857","kev_date_added":null,"published":"2025-09-25"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-20","vendors":["Rapid7"]},"summary":"Stored XSS in ScanName field allows attackers to execute scripts if configuration file is modified, impacting AppSpider Pro users.","url":"https://insights.sbomify.com/CVE-2025-4951/"}