CVE-2024-41637: raspap-webgui · Command Injection
Affects raspap-webguiSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 3.1.5 soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2024
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 26 Oct 2026.
What to do
Upgrade raspap/raspap-webgui to 3.1.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubraspap/raspap-webguipkg:github/raspap/raspap-webguiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-41637, organizations should immediately upgrade RaspAP to version 3.1.5 or later, where the vulnerability has been addressed. If upgrading is not immediately possible, restrict write permissions on the restapi.service file to prevent modification by the www-data user. Review and tighten sudoers configurations to ensure www-data cannot execute critical commands without password prompts. Implement strict access controls and network segmentation to limit exposure of the RaspAP management interface. Employ web application firewalls (WAFs) and intrusion detection systems (IDS) to monitor and block suspicious activities targeting the www-data user or REST API endpoints. Regularly audit system permissions and sudo privileges to detect and remediate insecure configurations. Additionally, monitor logs for unusual command executions or service modifications. Finally, consider isolating RaspAP instances in hardened containers or virtual machines to reduce the impact of potential compromises.
Description
RaspAP before 3.1.5 allows an attacker to escalate privileges: the www-data user has write access to the restapi.service file and also possesses Sudo privileges to execute several critical commands without a password.