{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-11195 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-11195 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11195 is a low-severity vulnerability in Rapid7 AppSpider Pro, published on 30 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-11195 and fix it if it is affected.\n\nWhat it is: CVE-2025-11195 is a low-severity vulnerability in Rapid7 AppSpider Pro, published on 30 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-11195 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-11195/ (Markdown: https://insights.sbomify.com/CVE-2025-11195/index.md)","id":"CVE-2025-11195","markdown":"https://insights.sbomify.com/CVE-2025-11195/index.md","name":"CVE-2025-11195","record":{"aliases":["GHSA-x5c4-2c4m-rfj5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rapid7 AppSpider Pro","requires_auth":"low_privilege","summary":"Attackers can modify project names in configuration files to duplicate existing names, bypassing uniqueness validation in Rapid7 AppSpider Pro.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"appspider_pro","vendor":"rapid7"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Rapid7 AppSpider Pro versions below 7.5.021 suffer from a project name validation vulnerability, whereby an attacker can change the project name directly in the configuration file to a name that already exists. This issue stems from a lack of effective verification of the uniqueness of project names when editing them outside the application in affected versions. This vulnerability was remediated in version 7.5.021 of the product.","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":"Rapid7 AppSpider Project Name Validation Bypass","id":"CVE-2025-11195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"External Login \u003c= 1.11.2 - Authenticated (Subscriber+) Sensitive Data Exposure via Test Connection","id":"CVE-2025-11196"},"packages":[],"prev":{"headline":"Information disclosure in Idea Tab Pro TB373FU","id":"CVE-2025-11193"},"products":["AppSpider Pro"],"published":"2025-09-30","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":4.6,"headline":"Cross-site scripting in AppSpider Pro","id":"CVE-2025-4951","kev_date_added":null,"published":"2025-05-20"},{"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-09-30","vendors":["Rapid7"]},"summary":"Attackers can modify project names in configuration files to duplicate existing names, bypassing uniqueness validation in Rapid7 AppSpider Pro.","url":"https://insights.sbomify.com/CVE-2025-11195/"}