LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27039: WordPress WZone plugin <= 14.0.31 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in AA-Team WZone woozone allows Blind SQL Injection.This issue affects WZone: from n/a through <= 14.0.31.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27039 is a high-severity SQL injection issue in the WordPress WZone plugin, also known as woozone, affecting versions through 14.0.31. An attacker with low-level privileges could potentially extract sensitive database information. No active exploitation is reported in the provided sources.

Executive priority

Prioritize remediation for public WordPress sites using this plugin, especially where many user accounts exist. The main business risk is unauthorized database disclosure. If the plugin is absent, this CVE is not directly applicable.

Technical view

The issue is CWE-89 improper neutralization in SQL commands, described as blind SQL injection. CVSS 3.1 is 8.5: network-accessible, low complexity, low privileges required, no user interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running AA-Team WZone/woozone version 14.0.31 or earlier. The CVSS vector indicates exploitation requires an authenticated low-privilege user, not anonymous access.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Because this is a recent high-severity WordPress plugin SQL injection, organizations should treat internet-facing sites with affected versions as priority review targets.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is stated as through 14.0.31. No exploit details, proof-of-concept status, or fixed version are provided in the source bundle.

Mitigation direction

  • Inventory WordPress sites for the WZone/woozone plugin and installed version.
  • Check AA-Team, WordPress, or Patchstack guidance for a fixed version or vendor workaround.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Limit unnecessary low-privilege WordPress accounts until remediation is complete.

Validation and detection

  • Confirm whether WZone/woozone is installed on each WordPress instance.
  • Verify whether the installed version is 14.0.31 or earlier.
  • Review user roles and remove unnecessary low-privilege accounts.
  • Check web and application logs for unusual plugin-related database errors or probing.
  • Track the CVE and Patchstack entry for updated remediation details.
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-27039 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
High
CVSS
8.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
8.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L3.14.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.5High
CVSS 3.1 vector shape for CVE-2026-27039Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
AA-TeamWZonewoozone, 0unaffected
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.