CVE-2026-50213
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 account validation endpoint /v1/User/validate returns comprehensive user profile data sheets, which can be crawled by iterating predictable identification strings.
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 confidenceThe /v1/User/validate endpoint exposes comprehensive user profile data without proper authorization checks. Attackers can harvest sensitive user information by iterating through predictable identification strings (e.g., sequential IDs), enabling large-scale user data enumeration.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 device model and firmware versionAccess the device admin interface or check the firmware version through the device settings or by querying the device's system information endpoint. For command-line access, use 'dmidecode' or check /etc/version on the device if SSH/telnet is available.Affected if The device is an Acer Connect M6e 5g with firmware version m6e_ai_1.00.000019 or earlier.
-
Verify the /v1/User/validate endpoint is exposedSend an HTTP GET request to http://<device-ip>/v1/User/validate without providing any authentication tokens or credentials. Use a tool like curl: curl -v http://<device-ip>/v1/User/validateAffected if The endpoint responds with an HTTP 200 status and returns user profile data without requiring authentication.
-
Test for user enumeration via sequential IDsSend multiple requests to /v1/User/validate with different ID values in the request (e.g., ?id=1, ?id=2, ?id=3 or varying numeric sequences). Compare the responses to see if different user records are returned.Affected if The endpoint accepts sequential or easily guessable numeric IDs and returns different user profile information for each request, allowing mass data exfiltration.
-
Inspect response for sensitive user dataExamine the HTTP response body from the /v1/User/validate endpoint. Look for personally identifiable information such as usernames, email addresses, phone numbers, or other profile details.Affected if The response contains sensitive user profile data (names, emails, phone numbers, addresses, or other PII) without any authorization token.
You are affected if you have an Acer Connect M6e 5g device running firmware m6e_ai_1.00.000019 or earlier and the /v1/User/validate endpoint returns user data without 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 dataImplement authentication and role-based authorization on the endpoint, and replace predictable identification strings with non-sequential identifiers (e.g., UUIDs) to prevent enumeration.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50213 — 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-50213 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