dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-36828

HIGH · 8.8 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 exists in the /cgi-bin/tools/ajax_cmd endpoint of Panabit PAP-XM320 up to and including v7.7. The CGI component allows authenticated users to execute arbitrary shell commands with root privileges via the action=runcmd 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 the /cgi-bin/tools/ajax_cmd CGI endpoint of Panabit PAP-XM320 (versions up to v7.7). Authenticated users can inject and execute arbitrary shell commands through the action=runcmd parameter with root privileges.

MitigationRestrict access to the /cgi-bin/tools/ajax_cmd endpoint to authorized personnel only, and upgrade to a patched version once available. Implement strict input validation on the action parameter.

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.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. Identify device model
    Access the device management interface or check hardware labeling to confirm the device is a Panabit PAP-XM320 model.
    Affected if The device is a Panabit PAP-XM320 unit.
  2. Check firmware version
    Log into the Panabit management console and navigate to the System or Status page to view the firmware version. Alternatively, check via CLI if available.
    Affected if The installed firmware version is v7.7 or any earlier version.
  3. Verify CGI endpoint accessibility
    Attempt to access the URL path /cgi-bin/tools/ajax_cmd on the device's web interface using a browser or curl command.
    Affected if The endpoint responds and is reachable from the network.
  4. Confirm authentication access
    Verify that you have valid administrator credentials for the Panabit management interface or can obtain them through legitimate channels.
    Affected if You can authenticate to the device management panel.
  5. Test vulnerable parameter
    If authorized, send a request to /cgi-bin/tools/ajax_cmd with the parameter action=runcmd and a test command (e.g., action=runcmd&cmd=echo+test).
    Affected if The command executes and returns output, confirming command injection is possible.

A defender is affected if they operate a Panabit PAP-XM320 device running firmware v7.7 or earlier where the /cgi-bin/tools/ajax_cmd endpoint is network-accessible with valid admin credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the /cgi-bin/tools/ajax_cmd endpoint to authorized personnel only, and upgrade to a patched version once available. Implement strict input validation on the action parameter.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-36828 — 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-2026-36828 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