dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-3453

HIGH · 8.1 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
The ProfilePress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.16.11. This is due to missing ownership validation on the change_plan_sub_id parameter in the process_checkout() function. The ppress_process_checkout AJAX handler accepts a user-controlled subscription ID intended for plan upgrades, loads the subscription record, and cancels/expires it without verifying the subscription belongs to the requesting user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to cancel and expire any other user's active subscription via the change_plan_sub_id parameter during checkout, causing immediate loss of paid access for victims.

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 · high confidence

The ProfilePress WordPress plugin fails to validate ownership of subscriptions in the ppress_process_checkout AJAX handler. The change_plan_sub_id parameter is directly used to load and cancel subscription records without verifying the subscription belongs to the authenticated user, allowing any authenticated subscriber to cancel arbitrary user subscriptions.

MitigationUpdate to ProfilePress version 4.16.12 or later which includes ownership validation. Until then, restrict AJAX ppress_process_checkout capability or add server-side ownership verification before processing subscription cancellations.

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
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Confirm ProfilePress plugin is installed
    Check your WordPress plugins directory or use WP-CLI: wp plugin list --name=profilepress
    Affected if ProfilePress is installed and active
  2. Identify the installed ProfilePress version
    Look in WordPress admin under Plugins > ProfilePress, or check the plugin header in /wp-content/plugins/profilepress/ folder for the Version line
    Affected if Version is lower than 4.16.12 (the fixed release)
  3. Verify the vulnerable AJAX handler exists
    Search the plugin files for 'ppress_process_checkout' function definition, typically in a file named like ajax.php or handlers.php within the ProfilePress plugin directory
    Affected if The AJAX handler function exists in the plugin code
  4. Confirm the change_plan_sub_id parameter handling lacks ownership validation
    Examine the process_checkout() function code - look for whether the subscription ID is validated against the current user before processing cancellation/expiry
    Affected if The code accepts the subscription ID without verifying it belongs to the requesting user
  5. Check if subscriber-level user accounts exist
    Review WordPress user roles at Users > All Users to see if any users with Subscriber role exist
    Affected if Any authenticated subscriber-level users can potentially exploit this IDOR vulnerability

You are affected if ProfilePress is installed with a version lower than 4.16.12 and the plugin handles subscription management with the vulnerable AJAX handler.

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 ProfilePress version 4.16.12 or later which includes ownership validation. Until then, restrict AJAX ppress_process_checkout capability or add server-side ownership verification before processing subscription cancellations.

Recommended fix Moderate confidence

ProfilePress version 4.16.12 or later (latest available version)

  1. 1. Log in to WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate ProfilePress plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown, manually download the latest version from wordpress.org/plugins/profilepress/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After update, verify the plugin version is greater than 4.16.11

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-3453 — 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-3453 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