Raspap WebguiApplication · Raspap

CVE-2025-50428

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-27
Fix available
A fix is available. Upgrade to after 3.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
In RaspAP raspap-webgui 3.3.2 and earlier, a command injection vulnerability exists in the includes/hostapd.php script. The vulnerability is due to improper sanitizing of user input passed via the interface parameter.

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 · high confidence

A command injection vulnerability exists in RaspAP raspap-webgui 3.3.2 and earlier. The includes/hostapd.php script fails to properly sanitize user input supplied via the 'interface' parameter, allowing an attacker to inject arbitrary operating system commands. This is exploitable remotely with no authentication required given the CVSS vector indicates network attack vector and low attack complexity.

MitigationImmediate remediation requires implementing strict input validation and output encoding for all user-supplied parameters, particularly the 'interface' parameter in hostapd.php. Consider applying the principle of least privilege to the web application process and deploying a WAF as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Raspap WebguiApplication
Affected:<= 3.3.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify RaspAP webgui installation
    Locate the raspap-webgui installation directory - common paths include /var/www/html/ or /opt/raspap/. Look for the presence of known RaspAP files such as index.php, config.php, or the includes/ directory.
    Affected if RaspAP is installed on the system and the web interface is accessible.
  2. Check installed raspap-webgui version
    Review the version information in the RaspAP installation. Check files like config.php, package.json, or any VERSION/CHANGELOG file within the raspap directory for version details. Compare the installed version against the affected range of <= 3.3.2.
    Affected if The installed version is 3.3.2 or any earlier version.
  3. Verify vulnerable file exists
    Confirm the presence of includes/hostapd.php in the RaspAP installation directory. This file handles hostapd management and contains the vulnerable 'interface' parameter handling.
    Affected if The file includes/hostapd.php exists and is part of the installed RaspAP version.
  4. Confirm hostapd management is accessible
    Determine if the hostapd management interface in RaspAP is accessible via the web. This typically involves accessing the Wireless AP configuration page. The vulnerability is exploitable when this functionality is reachable.
    Affected if The hostapd configuration interface is enabled and accessible without authentication.
  5. Inspect interface parameter handling
    Examine the includes/hostapd.php code for how the 'interface' parameter is processed. Look for instances where this parameter is used in system calls, exec functions, or shell commands without proper sanitization.
    Affected if The code passes the 'interface' parameter directly to shell execution functions without validation.

A system is affected if RaspAP raspap-webgui version 3.3.2 or earlier is installed, the includes/hostapd.php file exists, and the hostapd management interface is accessible via the web.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.3.2
Vendor patch github.com →
Interim mitigation

Immediate remediation requires implementing strict input validation and output encoding for all user-supplied parameters, particularly the 'interface' parameter in hostapd.php. Consider applying the principle of least privilege to the web application process and deploying a WAF as a defense-in-depth measure.

Recommended fix Moderate confidence
  1. Review the vendor patch at https://github.com/RaspAP/raspap-webgui/pull/1833 to understand the code changes made to includes/hostapd.php
  2. Identify the insecure usage of the 'interface' parameter in the affected code
  3. Apply the sanitization/validation changes from the patch to includes/hostapd.php, ensuring the interface parameter is properly validated before use in shell commands
  4. Verify the fix does not introduce regressions by testing the hostapd functionality
  5. If running a version older than 3.3.2, upgrade to the latest release after applying the patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Raspap Webgui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50428 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50428 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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