Skip to main content

WP Grid Builder CVE-2026-13756

| EUVDEUVD-2026-43118 HIGH
Improper Privilege Management (CWE-269)
2026-07-11 security@wordfence.com GHSA-9qvw-92r9-h632
8.8
CVSS 3.1 · Vendor: wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Subscriber-level account
  2. Delivery
    Authenticate to WordPress REST API
  3. Exploit
    POST crafted nested-array to /wpgb/v2/metadata update()
  4. Execution
    Overwrite own wp_capabilities meta
  5. Persist
    Gain Administrator role
  6. Impact
    Full site takeover / code execution

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid authenticated account at Subscriber level or above (PR:L) - the primary limiting factor, so sites without open/self-service user registration are substantially harder to exploit. The attack targets the specific REST endpoint /wp-json/wpgb/v2/metadata and abuses its update() handler, which must be reachable over the network (AV:N); the crafted request must set the wp_capabilities user meta via a nested-array payload. No user interaction is needed (UI:N) and attack complexity is low (AC:L). Exploitation is limited to sites running WP Grid Builder version 2.3.3 or earlier; sites that disable registration, restrict REST API access, or have already updated are not exposed.

Impact

Signals are largely consistent toward a genuine high priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) indicates a network-reachable, low-complexity attack needing only low privileges and no user interaction, yielding full confidentiality/integrity/availability impact via a resulting admin takeover. The one meaningful barrier is PR:L: the attacker must already hold a valid low-level account (Subscriber+), so exposure is highest on sites permitting open or self-service registration and lower on closed sites. No EPSS score, KEV entry, SSVC decision, or POC was provided in the intelligence, so widespread automated exploitation cannot be confirmed - the absence of these signals is a data gap, not evidence of low risk. Reported by Wordfence, the finding is credible; treat as high priority especially where user registration is enabled.

Exploit ScenarioDerived

An attacker registers (or acquires) a Subscriber account on a WordPress site running WP Grid Builder ≤ 2.3.3, then sends an authenticated POST to /wp-json/wpgb/v2/metadata with a crafted nested-array payload that writes administrator => 1 into their own wp_capabilities user meta. Because the update() handler skips authorization and meta-key validation, the account is instantly elevated to Administrator, granting full site control including plugin/theme editing and PHP code execution. No public POC was identified at time of analysis, but the low complexity (AC:L) makes weaponization straightforward.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 11, 2026

Privilege escalation in the WP Grid Builder WordPress plugin (versions ≤ 2.3.3) lets an authenticated Subscriber-or-above user promote their own account to Administrator by sending a crafted nested-array payload to the /wp-json/wpgb/v2/metadata REST endpoint. The endpoint's update() handler lacks both an authorization check and meta-key validation, so an attacker can overwrite their own wp_capabilities user meta. No public exploit has been identified at time of analysis, and the flaw is not on CISA KEV; with CVSS 8.8 and low attack complexity, it is a high-priority patch for any site running this plugin.

RemediationAI

Update WP Grid Builder to the first release above 2.3.3 as published on the vendor changelog (https://docs.wpgridbuilder.com/changelog/); the input data does not name an exact patched version, so no vendor-released patch version is independently confirmed here - verify the fixed build against the changelog before deploying. If an immediate update is not possible, reduce exposure by disabling open user registration (Settings → General → uncheck 'Anyone can register') so attackers cannot obtain the Subscriber account the attack requires, and by restricting or blocking access to the /wp-json/wpgb/v2/metadata REST route at the WAF/reverse-proxy layer; note that blocking the route may break legitimate plugin metadata operations, so test grid functionality afterward. Monitor for unexpected changes to wp_capabilities/role assignments and audit existing accounts for unauthorized administrators. Refer to the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/6a42e0e8-a8c7-4bc5-80ca-5ef69d1f0b6c?source=cve) for detection guidance.

Affected VersionsENISA

WP Grid Builder 0 ≤2.3.3

Affected Packages

euvd wp_grid_builder no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WP Grid Builder is a commercial WordPress plugin for building filterable/faceted content grids. The flaw lives in a custom WordPress REST API route (wpgb/v2/metadata) whose update() callback is intended to persist plugin metadata but performs neither a capability/permission check nor a whitelist of which meta keys may be written. This maps to CWE-269 (Improper Privilege Management): because arbitrary user_meta keys can be set, an attacker can target the special wp_capabilities meta that WordPress uses to store a user's role/capability map. Supplying a nested-array payload that sets administrator => true rewrites the caller's role. No CPE strings were supplied in the intelligence; the affected component is identified from the plugin slug and vendor changelog only.

Know when WordPress gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (wordfence) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable REST endpoint with no user interaction and low complexity, but requires an existing Subscriber account (PR:L); admin takeover yields full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (wordfence).

CVSS VectorVendor: wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

The WP Grid Builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.3.3. This is due to missing authorization and meta key validation in the update() handler for the /wp-json/wpgb/v2/metadata REST endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to Administrator by updating their own wp_capabilities user meta with a crafted nested array payload.

Executive ViewAI

Why It Matters

WP Grid Builder WordPress plugin (≤2.3.3) allows Subscriber-level users to escalate privileges to Administrator by exploiting a REST API authorization flaw in the metadata endpoint. This enables complete website compromise including data theft and malware injection. With CVSS 8.8 severity and no patch currently available, immediate mitigation is critical for any WordPress site running this plugin.

Business Impact: High
Compensating Controls

Disable WP Grid Builder plugin if operationally non-critical; if required, implement WAF rules blocking /wp-json/wpgb/v2/metadata endpoint access; restrict REST API to essential authenticated endpoints only; enable comprehensive audit logging for user role and capability modifications; conduct immediate access review for unauthorized role escalations.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
commercial WordPress grid plugin, common but not universally deployed
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy