CVE-2026-50214
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 · uneditedThe /v1/Plan service relies entirely on a shared global API token for full administrative management, allowing arbitrary creation of zero-cost network access plans.
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 confidenceThe /v1/Plan service uses a single shared global API token for all administrative operations, granting full control to anyone possessing this token. This allows attackers to create zero-cost network access plans without proper authorization or authentication controls.
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<= m6e_ai_1.00.000019CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label or system information to confirm it is an Acer Connect M6e 5g routerAffected if The device is not an Acer Connect M6e 5g model
-
Check the firmware versionAccess the router admin panel or use the command 'cat /proc/version' or check the firmware version in the web UI under 'System' or 'Status' to determine the exact firmware buildAffected if The firmware version is m6e_ai_1.00.000019 or earlier
-
Locate the API endpointInspect the router's web interface or API documentation to confirm the /v1/Plan service endpoint exists and is accessibleAffected if The /v1/Plan endpoint is present and exposed
-
Identify the authentication mechanismExamine the API requests to /v1/Plan using browser developer tools or a network proxy; look for an Authorization header or token parameter in requestsAffected if a single shared global token is used for all requests without per-user credentials
-
Check for per-user authorizationReview the API response headers and body when making requests to /v1/Plan to see if user-specific authentication tokens or session identifiers are required, or test creating a plan with the shared token to observe if authorization failsAffected if the same token grants full administrative access without any per-user validation or role checks
A user is affected if they are running Acer Connect M6e 5g firmware at version m6e_ai_1.00.000019 or lower and the /v1/Plan service accepts a single shared global token without per-user authentication.
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 the shared global API token with a proper role-based access control (RBAC) system using per-user or per-service tokens with least-privilege permissions, and immediately rotate the compromised token.
- Consultation8.0 h
- Implementation32.0 h
- Testing16.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 $17,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50214 — 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-50214 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