LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54007: WordPress Post Grid and Gutenberg Blocks Plugin <= 2.3.11 - PHP Object Injection Vulnerability

Deserialization of Untrusted Data vulnerability in PickPlugins Post Grid and Gutenberg Blocks post-grid allows Object Injection.This issue affects Post Grid and Gutenberg Blocks: from n/a through <= 2.3.11.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress Post Grid and Gutenberg Blocks plugin. A logged-in user could abuse unsafe data deserialization to make the site process attacker-controlled PHP objects, potentially leading to loss of confidentiality, integrity, or availability. The supplied sources do not show active exploitation.

Executive priority

Treat this as a high-priority WordPress plugin issue where the plugin is deployed, especially on public sites with many user accounts. It is not KEV-listed in the supplied data, so urgency should be driven by exposure, authentication scope, and business criticality.

Technical view

CVE-2025-54007 is CWE-502 deserialization of untrusted data in PickPlugins Post Grid and Gutenberg Blocks through version 2.3.11. The CVSS vector indicates network access, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running the PickPlugins Post Grid and Gutenberg Blocks plugin, package post-grid, at version 2.3.11 or earlier. The CVSS privileges-required field indicates attacker access to some authenticated account is needed.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of exploitation in the wild. Practical impact may depend on the vulnerable code path and available PHP object chains in a specific WordPress installation.

Researcher notes

The bundle does not include exploit details, proof-of-concept status, or a named fixed version. Because PHP object injection severity depends on reachable gadget chains and code paths, validate affected installations carefully without assuming universal remote code execution.

Mitigation direction

  • Inventory WordPress sites for the post-grid plugin and installed version.
  • Prioritize sites running Post Grid and Gutenberg Blocks 2.3.11 or earlier.
  • Check Patchstack and vendor guidance for the fixed version or recommended mitigation.
  • Restrict unnecessary WordPress account access while remediation is pending.
  • Back up affected sites before plugin updates or compensating changes.

Validation and detection

  • Confirm whether the post-grid plugin is installed on each WordPress site.
  • Record the installed plugin version and compare it with the affected range.
  • Review vendor or Patchstack advisories for patch availability and remediation status.
  • Check logs for suspicious authenticated activity against plugin-related functionality.
  • Verify remediation by confirming the plugin is no longer in the affected range.
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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
cve · low confidence lookup

CVE-2025-54007 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.8 (3.1)
Known Exploited
No
Published

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

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.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-54007Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
PickPluginsPost Grid and Gutenberg Blockspost-grid, 0unaffected
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.