dbcve.org
RaspapApplication

CVE-2022-39987

HIGH · 8.8 CVSS v3.1 Published 2023-08-01
Fix available
A fix is available. Upgrade to after 2.9.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
A Command injection vulnerability in RaspAP 2.8.0 thru 2.9.2 allows an authenticated attacker to execute arbitrary OS commands as root via the "entity" POST parameters in /ajax/networking/get_wgkey.php.

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 in RaspAP versions 2.8.0 through 2.9.2 allows authenticated attackers to execute arbitrary OS commands as root via unsanitized 'entity' POST parameters in /ajax/networking/get_wgkey.php. User-supplied input is directly passed to shell execution functions without proper validation, enabling complete system compromise.

MitigationUpgrade to a patched version of RaspAP. If immediate patching is not possible, restrict access to the affected endpoint via authentication and network controls, or temporarily disable the vulnerable functionality.

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
RaspapApplication
Affected:>= 2.8.0, <= 2.9.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Verify RaspAP installation exists
    Look for RaspAP web files in common locations such as /var/www/html/raspap, /var/www/raspap, or the web root directory. Check for the presence of the /ajax/networking/ directory.
    Affected if RaspAP web files are found in the system
  2. Identify installed RaspAP version
    Locate and read the version file (commonly includes.php, config.php, or a dedicated version file in the RaspAP installation directory). Compare the version number to the affected range 2.8.0 - 2.9.2.
    Affected if Installed version falls within >= 2.8.0 and <= 2.9.2
  3. Confirm vulnerable endpoint exists
    Check for the existence of the file /ajax/networking/get_wgkey.php within the RaspAP web directory.
    Affected if The file get_wgkey.php exists in the expected location
  4. Verify WireGuard feature is configured
    Check if WireGuard has been configured or enabled in RaspAP. Look for WireGuard-related configuration files, keys, or settings in the RaspAP config directory.
    Affected if WireGuard functionality has been set up in RaspAP
  5. Assess authentication status for the endpoint
    Review RaspAP authentication settings. Determine if the /ajax/networking/get_wgkey.php endpoint requires authentication or if authentication can be bypassed.
    Affected if Authentication is disabled, weak, or the endpoint is accessible without proper session validation

A user is affected if RaspAP is installed with a version between 2.8.0 and 2.9.2, the vulnerable get_wgkey.php file exists, WireGuard is configured, and the endpoint is accessible to authenticated users.

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 2.9.2
Interim mitigation

Upgrade to a patched version of RaspAP. If immediate patching is not possible, restrict access to the affected endpoint via authentication and network controls, or temporarily disable the vulnerable functionality.

Recommended fix Moderate confidence

RaspAP version 2.9.3 or later (latest stable release)

  1. 1. Backup your current RaspAP configuration and data
  2. 2. Access your Raspberry Pi via SSH or terminal
  3. 3. Update the package list: sudo apt update
  4. 4. Upgrade RaspAP to the latest version by running: sudo apt upgrade raspap
  5. 5. Alternatively, manually update by cloning the latest release from the official GitHub repository
  6. 6. After upgrade, verify the get_wgkey.php file has been updated and no longer contains vulnerable code
  7. 7. Restart the web server: sudo systemctl restart lighttpd
  8. 8. Test that the application functions correctly with the new version
Caveat Standard upgrade - ensure backup before proceeding

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

Fix this in Raspap Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-39987 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