CVE-2025-36857: Rapid7 Appspider Pro · Incorrect Default Permissions
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.1% chance of exploitation in 30 days – higher than 2% 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 25 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
European organizations should ensure that all instances of Rapid7 Appspider Pro are updated to version 7.5.021 or later, where this vulnerability has been fixed. Additionally, organizations should enforce strict file system permissions on directories used by Appspider Pro to prevent unauthorized users from placing or modifying configuration files outside their own scope. Implementing monitoring and alerting on changes to configuration directories can help detect unauthorized modifications. Limiting the number of users with local access to systems running Appspider Pro and applying the principle of least privilege will reduce the risk of exploitation. Regular audits of user permissions and configuration file integrity checks can further mitigate risks. Finally, organizations should consider isolating Appspider Pro environments to trusted users only and use endpoint security controls to prevent unauthorized file writes.
Description
Rapid7 Appspider Pro versions below 7.5.021, suffer from a broken access control vulnerability in the application's configuration file loading mechanism, whereby an attacker can place files in directories belonging to other users or projects. Affected versions allow standard users to add custom configuration files. These files, which are loaded in alphabetical order, can override or change the settings of the original configuration files, creating a security vulnerability. This issue stems from improper directory access management. This vulnerability was remediated in version 7.5.021 of the product.