LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32555: WordPress Boost plugin <= 2.0.4 - SQL Injection vulnerability

Unauthenticated SQL Injection in Boost <= 2.0.4 versions.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A critical SQL injection flaw is reported in the WordPress Boost plugin through version 2.0.4. An unauthenticated remote attacker may reach the vulnerable function without user interaction, potentially exposing database information and causing limited service disruption. The supplied sources do not establish active exploitation or identify a fixed release.

Executive priority

Treat confirmed Boost 2.0.4-or-earlier deployments as an urgent remediation priority because exploitation could expose sensitive database contents without authentication. Prioritize internet-facing sites and systems holding customer, credential, or regulated data. Avoid claiming compromise solely from version detection.

Technical view

CVE-2026-32555 is classified as CWE-89 with CVSS 3.1 score 9.3 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L). The report describes unauthenticated SQL injection in Boost 2.0.4 and earlier. Technical root-cause details, affected request paths, and a vendor-confirmed fixed version are absent from the bundle.

Likely exposure

Potential exposure includes network-accessible WordPress sites running Boost version 2.0.4 or earlier. Inventory confirmation is essential because the structured affected record lists versions as “n/a” and default status as unaffected, conflicting with the title and description.

Exploitation context

The vulnerability is remotely reachable, low complexity, requires no privileges, and requires no user interaction according to its CVSS vector. KEV status is false, and the supplied sources provide no evidence of active exploitation. This does not prove exploitation is absent.

Researcher notes

The public bundle establishes the vulnerability class and severity but lacks endpoint, parameter, root-cause, patch, and exploitation details. Its structured affected entry conflicts with the narrative by reporting versions as “n/a” and default status unaffected. Confirm scope and remediation directly with current vendor guidance before closing findings.

Mitigation direction

  • Inventory WordPress installations and identify every deployed Boost plugin version.
  • Consult current vendor and Patchstack guidance for a confirmed fixed release or official mitigation.
  • Update only to a vendor-confirmed fixed version; the supplied bundle identifies none.
  • Disable or remove affected instances where operationally acceptable until remediation is confirmed.
  • Preserve backups and increase database and web-request monitoring during remediation.

Validation and detection

  • Confirm the installed plugin identity and version from trusted administrative inventory.
  • Verify the installed release is vendor-confirmed as fixed, not merely newer than 2.0.4.
  • Review web, application, and database logs for anomalous unauthenticated requests or query errors.
  • Use an authorized, non-destructive scanner to confirm remediation without testing exploit payloads.
  • Check that disabled or removed plugin code is no longer publicly reachable.
Prepared
Confidence
medium
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-32555 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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2026-32555Attack 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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PixelYourSite ProfessionalBoostn/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

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