CVE-2026-39533
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 Broken Access Control in AWP Classifieds <= 4.4.4 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 Broken Access Control vulnerability in AWP Classifieds plugin/theme for versions up to 4.4.4. The flaw allows unauthenticated attackers to access resources or perform actions that should require proper authorization, likely due to missing capability checks or improper validation on sensitive endpoints.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm AWP Classifieds installationLocate the AWP Classifieds plugin or theme in the WordPress installation directory (wp-content/plugins or wp-content/themes). Check for folder names containing 'awp-classifieds', 'classifieds', or similar. If using WordPress admin, navigate to Plugins or Themes page and look for 'AWP Classifieds' in the list.Affected if AWP Classifieds plugin or theme is not found in the WordPress installation
-
Determine installed versionIf AWP Classifieds is found, check its version number. For plugins: open the main plugin PHP file and look for 'Version:' in the plugin header comments, or check the version column in WordPress admin under Plugins. For themes: check style.css header or theme details in Appearance > Themes.Affected if The installed version is 4.4.4 or lower (any version up to and including 4.4.4)
-
Identify sensitive endpointsReview the AWP Classifieds codebase for PHP files handling admin-level or user-specific actions such as data export, user management, settings modification, or data submission endpoints. Look for files in the plugin/theme directory that contain functions for creating, editing, or deleting classifieds, users, or settings.Affected if The plugin contains admin-action or user-management functionality accessible via HTTP requests without authentication checks
-
Test unauthenticated access to sensitive actionsUsing a web browser or HTTP tool (curl, Burp Suite), attempt to access or trigger sensitive AWP Classifieds functions directly without logging in. This includes submitting requests to endpoints that should require logged-in administrative or user privileges, such as classified submission, user profile updates, or data retrieval APIs.Affected if Requests to sensitive endpoints succeed without returning authorization errors (401/403) and without requiring valid authentication credentials
If AWP Classifieds version 4.4.4 or lower is installed and sensitive endpoints respond successfully to unauthenticated requests, the environment is affected by this broken access control vulnerability.
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 AWP Classifieds to a version newer than 4.4.4 that includes the access control fix. If no patched version is available, implement temporary web application firewall rules to block unauthorized access to sensitive endpoints until a fix is released.
- 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-39533 — 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-39533 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