dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-1222

HIGH · 7.2 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has an Arbitrary File Upload vulnerability, allowing privileged remote attackers to upload and execute web shell backdoors, thereby enabling arbitrary code execution on the server.

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 confidence

The PrismX MX100 AP controller by BROWAN COMMUNICATIONS contains an arbitrary file upload vulnerability that allows authenticated remote attackers to upload malicious files, including web shells, to the device. This enables full compromise of the AP controller through arbitrary code execution, potentially allowing attackers to pivot to connected network infrastructure.

MitigationRestrict file upload functionality to strictly validated file types with extension and MIME type checking, implement authentication and authorization controls, disable script execution in upload directories, and apply vendor patches if available. Network segmentation should be applied to limit exposure of the management interface.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 PrismX MX100 device in your environment
    Review your network inventory or scan for devices responding to the BROWAN COMMUNICATIONS PrismX MX100 management interface (typically ports 443, 80, or vendor-specific ports). Check device GUI or CLI for the exact model designation.
    Affected if The device model is confirmed as PrismX MX100 from BROWAN COMMUNICATIONS and the firmware is not patched to the latest vendor version.
  2. Verify file upload feature is accessible
    Log into the device management interface and navigate to firmware upgrade, configuration backup/restore, or logo/certificate upload sections. Confirm whether the file upload functionality is present and not disabled.
    Affected if The file upload feature exists and is enabled in the device configuration.
  3. Assess management interface network exposure
    Check if the PrismX MX100 management interface (HTTP/HTTPS) is accessible from untrusted networks or the internet. Review firewall rules, ACLs, and VPN configurations controlling access to the device management ports.
    Affected if The management interface is reachable from networks outside the trusted administrative zone.
  4. Review authentication enforcement on file upload
    Inspect the device authentication settings for the file upload endpoints. Verify whether unauthenticated or low-privilege users can access the upload functionality.
    Affected if The file upload endpoint does not require strong authentication or accepts sessions from low-privilege accounts.
  5. Inspect upload directories for unexpected files
    If you have CLI or filesystem access, examine common upload directories (such as /www, /upload, /tmp, or firmware upload staging areas) for suspicious files with extensions like .php, .sh, .asp, .jsp, or other web shell patterns.
    Affected if Unexpected script files are found in web-accessible or temporary directories on the device.

Your environment is affected if you have a PrismX MX100 AP controller with the file upload feature enabled and the management interface accessible to authenticated attackers.

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 file upload functionality to strictly validated file types with extension and MIME type checking, implement authentication and authorization controls, disable script execution in upload directories, and apply vendor patches if available. Network segmentation should be applied to limit exposure of the management interface.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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