LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27413: WordPress Profile Builder Pro plugin < 3.14.0 - SQL Injection vulnerability

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.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-27413 is a critical blind SQL injection in the WordPress Profile Builder Pro plugin before 3.14.0. An unauthenticated remote attacker may be able to query database data indirectly. For businesses, the main concern is potential exposure of sensitive WordPress or user data on affected sites.

Executive priority

Treat this as urgent for any public WordPress site using Profile Builder Pro. Prioritize upgrade verification because the issue is critical, remotely reachable, and may expose sensitive data. No active exploitation is confirmed in the provided sources.

Technical view

The CVE describes CWE-89 improper neutralization in Cozmoslabs Profile Builder Pro, affecting versions before 3.14.0. CVSS 3.1 is 9.3 with AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L. The listed impact is blind SQL injection, with high confidentiality impact and low availability impact.

Likely exposure

Internet-facing WordPress sites using Profile Builder Pro versions earlier than 3.14.0 are the likely exposure. The sources do not identify affected free editions, hosting platforms, or specific vulnerable endpoints.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates remote, unauthenticated exploitation without user interaction, which raises urgency even without confirmed exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The vulnerability is described as blind SQL injection before 3.14.0, but the provided sources do not include endpoint details, proof of concept, exploit status, or vendor-specific hardening steps.

Mitigation direction

  • Inventory WordPress sites for Profile Builder Pro installations.
  • Upgrade Profile Builder Pro to version 3.14.0 or later.
  • Check Cozmoslabs and Patchstack guidance for any additional remediation instructions.
  • Restrict administrative access and review database exposure as defense-in-depth.

Validation and detection

  • Confirm the installed Profile Builder Pro version on each WordPress site.
  • Verify sites are running version 3.14.0 or later.
  • Review web and database logs for unusual query errors or anomalous request patterns.
  • Document any exposed site that cannot be upgraded immediately.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27413 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2026-27413Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CozmoslabsProfile Builder Pron/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.