Rapid7 AppSpider Project Name Validation Bypass
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-345.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA AppSpider Pro (Rapid7) Fixed in 7.5.021
Timeline
- 2026-10-02 Threatist record created from CVE-2025-11195
- 2026-10-03 Alias added: GHSA-x5c4-2c4m-rfj5
References
More Rapid7 Appspider Pro vulnerabilities
- TI-2017-03347 Untrusted search path in Rapid7 AppSpider Pro CVSS 3.0HIGH 7.8
- TI-2017-03344 Untrusted search path in Rapid7 AppSpider Pro CVSS 3.1HIGH 7.8
- TI-2017-03351 Memory corruption in Rapid7 AppSpider Pro CVSS 3.0HIGH 7.5
- TI-2025-04439 Cross-site scripting in Rapid7 AppSpider Pro CVSS 3.1MEDIUM 4.6
- TI-2025-24951 Rapid7 Appspider Broken Access Control Vulnerability CVSS 3.1LOW 3.3
Sources
- CVE-2025-11195 · CVE Program
- CVE-2025-11195 · NVD
- FIRST EPSS
- GHSA-x5c4-2c4m-rfj5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences