CVE-2026-54184
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 · uneditedUnauthenticated Insecure Direct Object References (IDOR) in Clean Login <= 1.15 versions.
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 confidenceUnauthenticated Insecure Direct Object Reference (IDOR) vulnerability in Clean Login plugin versions 1.15 and earlier allows remote attackers to access or modify objects (such as user data, sessions, or protected resources) without proper authorization by manipulating object references in HTTP requests.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 if Clean Login plugin is installedCheck your WordPress plugins directory or admin panel for 'Clean Login' plugin. Common paths: wp-content/plugins/clean-login/ or via WP-CLI: wp plugin list --search=clean-loginAffected if Clean Login plugin is present in the WordPress installation
-
Determine installed plugin versionCheck the plugin main file (usually clean-login.php) for the Version header, or inspect plugin metadata via WordPress admin > Plugins > Clean Login, or use WP-CLI: wp plugin get clean-login --format=jsonAffected if Version is 1.15 or earlier, or version cannot be determined (assume vulnerable)
-
Verify unauthenticated endpoint exposureTest accessing common Clean Login endpoints without authentication: /wp-json/clean-login/v1/ or similar REST routes, login/registration forms, or user profile pages. Use curl or browser to request these endpoints without providing credentials.Affected if Endpoints return user data, session info, or allow modifications without requiring authentication
-
Check for IDOR in object referencesInspect HTTP requests to Clean Login plugin endpoints. Look for parameters that reference user IDs, session tokens, or object handles (e.g., ?user_id=1, ?session=abc). Modify these values in requests to see if unauthorized access occurs.Affected if Changing object references (user IDs, session IDs) in requests yields access to data or actions for other users without authorization errors
Environment is affected if Clean Login plugin version 1.15 or earlier is installed AND unauthenticated endpoints are accessible, allowing unauthorized access or modification of objects by manipulating reference values in HTTP requests.
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 dataUpgrade Clean Login plugin to version newer than 1.15; if no patch available, implement proper object-level authorization checks on all sensitive endpoints and validate user permissions before allowing access to any resource.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54184 — 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-54184 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