CVE-2025-11195: Rapid7 AppSpider Project Name Validation Bypass
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-11195?
CVE-2025-11195 is categorized as a medium severity vulnerability due to its potential for unauthorized access to project configurations.
How do I fix CVE-2025-11195?
To fix CVE-2025-11195, upgrade Rapid7 AppSpider Pro to version 7.5.021 or later, which addresses the project name validation issue.
What types of attacks can exploit CVE-2025-11195?
Attackers can exploit CVE-2025-11195 to overwrite existing project names in the configuration file, potentially leading to unauthorized project manipulation.
Who is affected by CVE-2025-11195?
CVE-2025-11195 affects all versions of Rapid7 AppSpider Pro below 7.5.021.
What causes CVE-2025-11195?
CVE-2025-11195 is caused by insufficient verification of project name uniqueness in the configuration file.