CVE-2026-1202
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 security flaw has been discovered in CRMEB up to 5.6.3. The affected element is the function appleLogin of the file crmeb/app/api/controller/v1/LoginController.php. Performing a manipulation of the argument openId results in improper authentication. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceCRMEB up to version 5.6.3 contains an authentication bypass vulnerability in the Apple login functionality. The appleLogin function in LoginController.php fails to properly validate the openId parameter, allowing remote attackers to manipulate this argument to gain unauthorized access to user accounts. The vulnerability has a public exploit and can be exploited remotely.
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<= 5.6.3CVSS 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.
-
Locate the LoginController.php fileSearch the web root directory for the file 'LoginController.php', typically found in application/controller/ or app/api/controller/. Use: find /path/to/webroot -name LoginController.php 2>/dev/nullAffected if The file exists and contains an appleLogin function - this indicates the vulnerable code is present
-
Determine the installed CRMEB versionCheck version files such as version.php, composer.json, or config/app.php in the CRMEB installation directory. Compare the version number to the affected range: <= 5.6.3Affected if The installed version is 5.6.3 or any lower version number
-
Verify the appleLogin function existsOpen LoginController.php and search for the function 'function appleLogin' or 'public function appleLogin'. Confirm the function accepts an openId parameterAffected if The appleLogin function exists and accepts an openId parameter without proper validation
-
Inspect openId parameter validationWithin the appleLogin function in LoginController.php, examine how the openId parameter is handled. Look for validation logic such as empty() checks, length validation, format verification, or database lookup validationAffected if The openId parameter is used directly in authentication logic without validation, or validation is missing/insufficient (e.g., no check if openId is empty, no format validation, no user lookup)
-
Check endpoint accessibilityDetermine if the appleLogin endpoint is publicly accessible via routing. Common paths include /api/login/apple or /app/login/apple. Attempt a request or check route configuration filesAffected if The appleLogin endpoint is exposed without additional authentication guards
You are affected if CRMEB version is 5.6.3 or lower AND the LoginController.php contains an appleLogin function where the openId parameter lacks proper validation before being used in authentication logic.
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 dataDisable the Apple login functionality until a vendor patch is available; alternatively, implement strict server-side validation of the openId parameter against Apple's identity token and add rate limiting on authentication endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1202 — 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-1202 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