dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3445

HIGH · 7.1 CVSS v3.1 Published 2026-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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 Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress plugin for WordPress is vulnerable to unauthorized membership payment bypass in all versions up to, and including, 4.16.11. This is due to a missing ownership verification on the `change_plan_sub_id` parameter in the `process_checkout()` function. This makes it possible for authenticated attackers, with subscriber level access and above, to reference another user's active subscription during checkout to manipulate proration calculations, allowing them to obtain paid lifetime membership plans without payment via the `ppress_process_checkout` AJAX action.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the ProfilePress WordPress plugin. Authenticated users with subscriber-level access can manipulate the `change_plan_sub_id` parameter during checkout to reference another user's active subscription, bypassing payment by manipulating proration calculations via the `ppress_process_checkout` AJAX action.

MitigationUpdate to version 4.16.12 or later which implements proper ownership verification on the subscription ID parameter to ensure users can only modify their own subscriptions.

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

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

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

  1. Identify ProfilePress plugin version
    Navigate to WordPress dashboard > Plugins > Installed Plugins, locate ProfilePress, and note the version number displayed. Alternatively, inspect the plugin header in /wp-content/plugins/profilepress/ folder.
    Affected if The installed version is lower than 4.16.12 (vulnerable). Versions 4.16.12 and later contain the fix.
  2. Verify subscriber-level user access exists
    Check WordPress Users > All Users for any user with the 'Subscriber' role. This role is required for the exploit.
    Affected if At least one subscriber-level user account exists on the site, creating a potential attack vector.
  3. Confirm subscription functionality is active
    Navigate to ProfilePress settings and verify that any payment plans or subscription packages have been created and enabled. Inspect the database table pp_subscription_plans or check the admin UI for active plans.
    Affected if Subscription plans or payment packages are configured and active on the site.
  4. Inspect AJAX endpoint accessibility
    Check the plugin code for the ppress_process_checkout AJAX action registration (look for add_action('wp_ajax_ppress_process_checkout', ...) and verify if it requires authentication or any capability check).
    Affected if The AJAX endpoint is accessible to authenticated users (including subscribers) without additional capability verification.

If ProfilePress version is below 4.16.12 AND subscriber accounts exist AND subscription plans are configured, the environment is affected by this vulnerability.

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 version 4.16.12 or later which implements proper ownership verification on the subscription ID parameter to ensure users can only modify their own subscriptions.

Recommended fix Moderate confidence

ProfilePress version 4.16.12 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the ProfilePress plugin
  4. 4. Check the current version installed
  5. 5. If the installed version is 4.16.11 or lower, update to the latest available version

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