CVE-2026-57355
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 · uneditedSubscriber Broken Access Control in Classified Listing <= 5.4.2 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 confidenceBroken Access Control vulnerability in Classified Listing WordPress plugin versions <= 5.4.2 allows authenticated subscriber-level users to access functionality or data that should be restricted to higher-privilege roles.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Confirm Classified Listing plugin is installedNavigate to WordPress admin > Plugins and locate the 'Classified Listing' plugin in the list of installed plugins. Note whether it is active or inactive.Affected if Plugin is installed and active
-
Check installed plugin versionIn the Plugins list, click on the plugin details link or view the plugin file header (typically /wp-content/plugins/classified-listing/readme.txt or main plugin PHP file) to find the Version: X.X.X entry. Compare this version to the affected range <= 5.4.2.Affected if Installed version is 5.4.2 or lower
-
Verify presence of subscriber-level user accountsNavigate to WordPress admin > Users and review the user list. Look for any users assigned the 'Subscriber' role specifically.Affected if At least one user with Subscriber role exists in the system
-
Review user role capabilities for plugin-related functionalityCheck the Classified Listing plugin settings or capabilities configuration (typically under Listings > Settings or similar) to determine what user roles can access listing creation, management, or admin functions. Compare the allowed roles against the Subscriber role.Affected if Subscriber role is granted permissions to create, edit, or manage listings or classifieds
User is affected if the Classified Listing plugin version is 5.4.2 or lower, the plugin is active, and subscriber-level users exist with access to plugin functionality that should be restricted to higher-privilege roles.
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.
dbcve · scopedUpdate Classified Listing plugin to version 5.4.3 or later which contains the access control fix; alternatively implement proper capability checks on affected endpoints.
Classified Listing plugin version 5.4.3 or latest available version
- Upgrade the Classified Listing plugin to version 5.4.3 or later from the official WordPress plugin repository
- Verify the upgrade was successful by checking the plugins page in WordPress admin
- Confirm that subscriber-level users no longer have unauthorized access to listing management functions
- Review user roles and permissions to ensure only appropriate roles have access to classified listing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57355 — 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-57355 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