dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39433

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Subscriber Arbitrary Content Deletion in WPAMS < 49.5.3 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 confidence

WPAMS plugin before version 49.5.3 lacks proper authorization checks, allowing authenticated users with Subscriber role to delete arbitrary content on the WordPress site. This is a broken access control/IDOR vulnerability where the plugin fails to verify user permissions before executing delete operations.

MitigationUpgrade WPAMS plugin to version 49.5.3 or later. Until patched, consider restricting or monitoring subscriber-level accounts.

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Check if WPAMS plugin is installed
    Navigate to WordPress admin > Plugins, or inspect /wp-content/plugins/ directory for WPAMS folder
    Affected if WPAMS plugin exists in the plugins directory
  2. Determine installed WPAMS version
    In WordPress admin, go to Plugins > WPAMS > View Details, or read version from plugin header in wp-content/plugins/wpams/wpams.php
    Affected if Version is lower than 49.5.3 or version cannot be determined (older install)
  3. Identify subscriber-level user accounts
    In WordPress admin, go to Users > All Users and check for any users with Subscriber role
    Affected if At least one Subscriber role account exists on the site
  4. Verify delete functionality is accessible to subscribers
    Attempt to access WPAMS delete endpoints or inspect plugin code for AJAX actions or front-end links available to Subscriber role users
    Affected if Delete operations are reachable/performed by authenticated users with Subscriber role without admin-level verification

The environment is affected if WPAMS plugin version is below 49.5.3 AND at least one Subscriber role account exists and can access the plugin's delete 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

Upgrade WPAMS plugin to version 49.5.3 or later. Until patched, consider restricting or monitoring subscriber-level accounts.

Recommended fix Moderate confidence

49.5.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WPAMS in the plugin list
  4. 4. Check the current installed version of WPAMS
  5. 5. If the installed version is below 49.5.3, click 'Update Now' to update to the latest version
  6. 6. Verify the update completed successfully and the new version is 49.5.3 or higher
  7. 7. Test that subscribers can no longer delete arbitrary content (confirm the authorization check is now properly enforced)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39433 — 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-39433 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