dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-42726

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Strategy11 Team AWP Classifieds another-wordpress-classifieds-plugin allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AWP Classifieds: from n/a through <= 4.4.5.

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 confidence

Missing Authorization vulnerability in the AWP Classifieds WordPress plugin (another-wordpress-classifieds-plugin) allows attackers to exploit incorrectly configured access control security levels. This broken access control issue affects versions through 4.4.5, potentially enabling unauthorized users to access privileged functionality or sensitive data that should require proper authentication and authorization checks.

MitigationUpdate to the latest version of AWP Classifieds when available, or apply proper authorization checks on all affected functions/endpoints. Conduct access control review across the plugin to ensure all admin-level operations verify user permissions.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the AWP Classifieds plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'AWP Classifieds' (or 'another-wordpress-classifieds-plugin'). The version number is displayed below the plugin name. Alternatively, inspect the main plugin PHP file (typically named awp-classifieds.php or similar) and check the plugin header comment for the Version field.
    Affected if The installed version is 4.4.5 or any earlier version (e.g., 4.4.4, 4.4.0, etc.)
  2. Compare your version against the affected range
    Review the version number found in the previous step. According to the CVE, all versions through 4.4.5 are affected, meaning versions 4.4.5, 4.4.4, 4.4.3, and below are within the vulnerable range.
    Affected if Your installed version is 4.4.5 or lower
  3. Identify if the plugin exposes administrative or privileged functions
    Examine the plugin directory (wp-content/plugins/awp-classifieds or similar) for PHP files containing function definitions related to data creation, modification, deletion, or sensitive data retrieval. Look for AJAX handlers, admin pages, or API endpoints within the plugin.
    Affected if The plugin contains functionality that handles sensitive operations or data without visible role/capability checks in the code
  4. Test for unauthorized access to plugin features
    Using a low-privileged WordPress user account (e.g., Subscriber or Contributor role), attempt to access plugin admin pages or trigger plugin-specific actions that should require administrator privileges. Check if the application returns expected 401/403 errors or allows the operation.
    Affected if A user account lacking administrative capabilities can access or modify plugin settings, classified listings, or other privileged functionality

You are affected if the AWP Classifieds plugin version installed is 4.4.5 or lower, as this version range contains the missing authorization vulnerability that allows improperly authorized access to privileged functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of AWP Classifieds when available, or apply proper authorization checks on all affected functions/endpoints. Conduct access control review across the plugin to ensure all admin-level operations verify user permissions.

Recommended fix Moderate confidence

Latest version of AWP Classifieds plugin (version higher than 4.4.5)

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the AWP Classifieds plugin (also known as 'another-wordpress-classifieds-plugin')
  4. 4. Check the current installed version number
  5. 5. If the installed version is 4.4.5 or below, update the plugin to the latest available version
  6. 6. After updating, verify the plugin functions correctly on your site
  7. 7. Test that the authorization controls are working as expected
Caveat Review the plugin's changelog for any breaking changes between your current version and the new version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42726 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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