CVE-2025-11195: Rapid7 AppSpider Pro · Improper Input Validation
Affects Rapid7 AppSpider ProSource CVE Database V5
Not known to be exploited · CVSS 3.3 Low.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rapid7 AppSpider Pro | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should prioritize upgrading Rapid7 AppSpider Pro to version 7.5.021 or later, where the issue has been resolved. Until the update is applied, organizations should enforce strict access controls to limit who can access and modify configuration files, ensuring only trusted administrators have such permissions. Monitoring and auditing changes to configuration files can help detect unauthorized modifications. Additionally, implementing file integrity monitoring solutions can alert administrators to unexpected changes in project configuration files. Organizations should also educate users about the risks of manual configuration edits and establish policies to prevent editing configuration files outside the application interface. Finally, segregating duties and using role-based access controls within the application can reduce the risk of low-privilege users exploiting this vulnerability.
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.