Project name collision via unchecked configuration editing
Published Sep 30, 2025 · Updated Sep 30, 2025
Improper input validation in Rapid7 AppSpider Pro before 7.5.021 allows local users to duplicate a project name via its configuration file. The UI checks project-name uniqueness, but loading an externally edited configuration accepts a name already assigned to another project. A low-privileged local user must be able to edit the file; the demonstrated consequence is a project-name collision and associated integrity loss.
Summary
What happened
Improper input validation in Rapid7 AppSpider Pro before 7.5.021 allows local users to duplicate a project name via its configuration file. The UI checks project-name uniqueness, but loading an externally edited configuration accepts a name already assigned to another project. A low-privileged local user must be able to edit the file; the demonstrated consequence is a project-name collision and associated integrity loss.
The record
- CVE
- CVE-2025-11195
- Published
- Sep 30, 2025
- Updated
- Sep 30, 2025
- Vendor
- Rapid7
- Product
- AppSpider Pro
- Classifications
- CWE-20, CWE-345, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 30, 2025CVE publishedPublication date reported by the CVE source.
- Sep 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.5.021
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo