dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-27413

CRITICAL · 9.3 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Cozmoslabs Profile Builder Pro allows Blind SQL Injection.This issue affects Profile Builder Pro: from n/a before 3.14.0.

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

A blind SQL injection vulnerability exists in Cozmoslabs Profile Builder Pro (a WordPress user management plugin) affecting versions before 3.14.0. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized user input, potentially enabling data exfiltration or privilege escalation.

MitigationUpgrade Profile Builder Pro to version 3.14.0 or later which contains the security patch. If immediate upgrade is not possible, disable the plugin until patched.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

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. Verify Profile Builder Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Profile Builder Pro' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder starting with 'profile-builder'.
    Affected if The plugin is installed and active in WordPress
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and click on 'Profile Builder Pro' to view the version, or check the plugin's main PHP file header for the 'Version' tag.
    Affected if Version is present and less than 3.14.0 (e.g., 3.13.x, 3.12.x, earlier versions)
  3. Identify exposed user input forms
    Check if any Profile Builder forms (registration, login, profile edit) are published on the site via shortcodes like [wppb-register], [wppb-login], or [wppb-edit-profile] placed on pages accessible to unauthenticated users.
    Affected if Public-facing forms exist that accept user input without authentication
  4. Review access to vulnerable plugin endpoints
    Inspect the site's public-facing URLs and forms that process Profile Builder data. The plugin typically handles user input at /wp-admin/admin-ajax.php or front-end form submissions. Check which actions are available to unauthenticated users.
    Affected if Unauthenticated users can submit data to Profile Builder endpoints (actions starting with 'wppb_' or similar)
  5. Inspect web application logs for SQL injection patterns
    Review web server access logs (Apache/nginx) and WordPress debug logs for suspicious query patterns in Profile Builder-related requests. Look for SQL keywords (UNION, SELECT, INSERT) or unusual characters in parameters that might indicate injection attempts.
    Affected if Suspicious SQL-like patterns appear in requests targeting Profile Builder functionality

If Profile Builder Pro version is below 3.14.0 AND the plugin is active with publicly accessible forms accepting unauthenticated user input, the environment is affected by this blind SQL injection 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

Upgrade Profile Builder Pro to version 3.14.0 or later which contains the security patch. If immediate upgrade is not possible, disable the plugin until patched.

Recommended fix Moderate confidence

Profile Builder Pro 3.14.0

  1. Backup your WordPress site and database before making any changes
  2. Verify your current Profile Builder Pro version by navigating to Plugins in WordPress admin
  3. Update Profile Builder Pro to version 3.14.0 or later through the WordPress plugin repository or your plugin management system
  4. After updating, clear any caching mechanisms if applicable
  5. Verify the update was successful by checking the plugin version in WordPress admin

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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