dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-3309

MEDIUM · 6.5 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 →
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
The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content – ProfilePress plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 4.16.11. This is due to the plugin allowing user-supplied billing field values from the checkout process to be interpolated into shortcode template strings that are subsequently processed without proper sanitization of shortcode syntax. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes by submitting crafted billing field values during the checkout process.

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 sanitize billing field inputs from the checkout process before inserting them into shortcode template strings. This allows unauthenticated attackers to inject arbitrary shortcode syntax via crafted billing field values during checkout, leading to arbitrary shortcode execution.

MitigationUpdate the plugin to version 4.16.12 or later. If an update is unavailable, disable the checkout functionality until a patched version can be deployed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Check ProfilePress plugin version
    In WordPress admin, go to Plugins > Installed Plugins > ProfilePress and note the version number. Alternatively, check the main plugin file (profilepress.php) for the 'Version' header.
    Affected if Version is lower than 4.16.12 (vulnerable versions)
  2. Verify plugin is active
    Confirm ProfilePress is activated in Plugins > Installed Plugins.
    Affected if Plugin is active and version is below 4.16.12
  3. Identify if checkout forms with billing fields exist
    Go to ProfilePress > Checkouts (or Forms) and list any checkout or registration forms that include billing address fields. These forms interpolate user-submitted billing data into shortcode templates.
    Affected if Active checkout forms with billing fields are present in vulnerable plugin versions
  4. Inspect shortcode templates for billing field interpolation
    Edit the checkout form templates and look for shortcode usage that includes billing field placeholders (such as [cp-checkout-billing-address] or similar billing-related shortcodes) without evident sanitization wrappers.
    Affected if Billing fields are rendered via shortcodes in templates on vulnerable versions

User is affected if ProfilePress plugin version is below 4.16.12 AND active checkout forms exist that use shortcode templates to render billing field values.

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 the plugin to version 4.16.12 or later. If an update is unavailable, disable the checkout functionality until a patched version can be deployed.

Recommended fix Moderate confidence

Latest version beyond 4.16.11 (check WordPress plugin repository for current stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate ProfilePress (Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content)
  4. Check the current installed version under the plugin name
  5. If the installed version is 4.16.11 or lower, click 'Update Now' to install the latest patched version
  6. Alternatively, download the latest version from the WordPress plugin repository at plugins.trac.wordpress.org
  7. After updating, verify the version number reflects the patched release

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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