CVE-2026-36827
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 · uneditedA command injection vulnerability exists in Panabit PAP-XM320 up to and including V7.7. The web management interface invokes the backend helper /usr/sbin/pappiw and passes user-controlled parameters to it. The helper performs unsafe argument processing using eval, which allows command injection when attacker-controlled input is included in the arguments. As a result, an authenticated remote attacker with access to the management interface may execute arbitrary shell commands.
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 confidenceCommand injection vulnerability in Panabit PAP-XM320 (up to V7.7) web management interface. The backend helper /usr/sbin/pappiw uses unsafe eval-based argument processing for user-controlled parameters passed from the web interface, allowing authenticated remote attackers to inject and execute arbitrary shell commands.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
-
Identify installed Panabit versionAccess the web management interface and locate the version information, typically found in the system status or about page. Alternatively, check via CLI using 'panapt show version' or similar command if available.Affected if The installed version is V7.7 or any version lower than V7.7 (versions up to and including V7.7 are affected).
-
Verify web management interface exposureDetermine if the Panabit web management interface (typically ports 80/443) is accessible from untrusted networks. Review firewall rules and network configurations to assess exposure.Affected if The web management interface is accessible from outside the trusted administrative network.
-
Inspect the pappiw binaryCheck if the file /usr/sbin/pappiw exists on the system. If accessible, examine its contents or behavior for eval-based argument processing patterns.Affected if The binary /usr/sbin/pappiw exists and uses eval for argument processing.
-
Review for compromise indicatorsExamine running processes for unexpected shell commands, check web server logs for suspicious parameter values, and look for new or unexpected files in system directories.Affected if Unexpected shell processes are running, web logs contain suspicious parameter patterns, or unauthorized files appear on the system.
A system is affected if it runs Panabit PAP-XM320 version V7.7 or lower AND has its web management interface accessible to potential attackers, with the vulnerable pappiw binary present.
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.
From vendor dataReplace unsafe eval usage with secure function calls or argument passing mechanisms, implement strict input validation/sanitization, and apply vendor patch when released. Restrict management interface access to trusted networks.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36827 — 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-36827 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