CVE-2026-55742
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 · uneditedCotonti 1.0.0 (master branch, commit f43f1fc3) is vulnerable to Cross-Site Request Forgery in the administration rights handler. In system/admin/admin.rights.php, the rights update action ('a=update') modifies group access rights (including via cot_auth_add_group) without calling cot_check_xg to validate the anti-CSRF token.
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 confidenceCotonti 1.0.0 is vulnerable to CSRF in the administration rights handler. The rights update action in system/admin/admin.rights.php modifies group access rights without validating the anti-CSRF token via cot_check_xg(), allowing an authenticated administrator to be tricked into granting elevated permissions to an attacker-controlled group, achieving privilege escalation to administrator.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Verify Cotonti installation and versionCheck if the file system/admin/admin.rights.php exists in your web root. Examine any version file (like version.php or about.php) to confirm the installed Cotonti version is 1.0.0Affected if The version is 1.0.0 and the affected file exists
-
Examine the rights update handler for CSRF validationOpen system/admin/admin.rights.php and locate the code block that handles the 'a=update' action. Search for occurrences of 'cot_check_xg' within that blockAffected if The 'a=update' action handler exists but does NOT contain a call to cot_check_xg() for anti-CSRF validation before processing the rights modification
-
Confirm admin interface accessibilityCheck if the Cotonti administration panel is accessible at /admin.php or similar endpoint and whether authentication is properly enforcedAffected if An authenticated administrator session can access the rights management interface
-
Identify exposed attack surfaceDetermine if the application configuration permits group creation or modification by lower-privileged users, as this would be required for the privilege escalation chainAffected if Group creation or modification functionality is available that could be leveraged alongside the CSRF vulnerability
You are affected if running Cotonti 1.0.0 with system/admin/admin.rights.php present and the 'a=update' action handler lacks cot_check_xg() validation before processing group rights modifications.
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 dataAdd cot_check_xg() validation in admin.rights.php before processing the rights update action ('a=update') to verify the anti-CSRF token.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55742 — 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-55742 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