CVE-2026-24788
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRaspAP raspap-webgui versions prior to 3.3.6 contain an OS command injection vulnerability. If exploited, an arbitrary OS command may be executed by a user who can log in to the product.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn authenticated OS command injection vulnerability exists in raspap-webgui versions prior to 3.3.6. A user who can log into the web interface can inject and execute arbitrary operating system commands on the underlying host, potentially leading to full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify RaspAP installation existsLook for RaspAP directories on the system. Common locations include /var/www/html/raspap, /opt/raspap, or within the web server root. Check if the raspap-webgui directory or files are present.Affected if RaspAP is installed on the system
-
Determine installed raspap-webgui versionLocate the version file or code that contains the version string. Check files like version.php, package.json, or the main index.php for a version number or tag. Compare your found version to the affected range (versions prior to 3.3.6).Affected if Installed version is lower than 3.3.6
-
Confirm web interface is accessibleCheck if the RaspAP web service is running. This may involve checking the web server status (apache2, nginx, lighttpd) or if port 80/443 is listening. Attempt to access the web interface URL if known.Affected if The RaspAP web interface is running and network-accessible
-
Verify authentication configurationCheck if the RaspAP web interface requires authentication. Look for authentication settings in the configuration files or try accessing the interface to see if a login prompt appears.Affected if The web interface allows authenticated users to access input parameters without proper sanitization
The environment is affected if RaspAP raspap-webgui version is found to be below 3.3.6 and the web interface is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade raspap-webgui to version 3.3.6 or later to obtain the patched code. Limit administrative access to trusted users only and apply network segmentation as a compensating control until patching is feasible.
3.3.6
- Upgrade RaspAP raspap-webgui to version 3.3.6 or later to remediate the OS command injection vulnerability.
- Verify the upgrade by checking the webgui version in the admin interface after updating.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24788 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data