CVE-2025-66058
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-66058 is a Missing Authorization (Broken Access Control) vulnerability in the PickPlugins Post Grid and Gutenberg Blocks WordPress plugin that allows authenticated low-privileged users to access restricted application data. It affects all versions of the plugin through 2.3.17, with version 2.3.18 containing the fix. The vulnerability was reported by Abu Hurayra on September 4, 2025, published by Patchstack on October 4, 2025, and assigned a CVE on December 18, 2025. It carries a CVSS v3.1 base score of 6.5 (Medium) (Patchstack, Red Hat CVE).

Technical details

The vulnerability is classified as CWE-862 (Missing Authorization), meaning one or more functions within the plugin fail to perform adequate authorization checks before executing privileged operations. An authenticated attacker with as little as Subscriber-level access can exploit this flaw over the network without any user interaction or complex conditions, allowing them to access data or functionality that should be restricted to higher-privileged roles. The root cause is the absence of a proper authorization, authentication, or nonce token check in a plugin function, consistent with OWASP Top 10 category A5: Broken Access Control (Patchstack).

Impact

Successful exploitation allows authenticated low-privileged users (e.g., Subscribers) to read sensitive information that should be restricted by access controls, resulting in a high confidentiality impact with no effect on integrity or availability. The vulnerability's network-accessible attack vector means any registered user on an affected WordPress site could exploit it remotely. While lateral movement is not directly enabled, exposure of sensitive post or configuration data could facilitate further attacks or information gathering (Patchstack, Red Hat CVE).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported for CVE-2025-66058 at this time. The EPSS score is approximately 0.028%, indicating a low current probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, Patchstack notes that vulnerabilities of this class are commonly used in mass-exploit campaigns targeting thousands of WordPress sites regardless of their size or popularity (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Post Grid and Gutenberg Blocks plugin (by PickPlugins) at version 2.3.17 or earlier, using tools like WPScan or by checking the plugin's readme.txt file at https://target.com/wp-content/plugins/post-grid/readme.txt.
  2. Obtain low-privileged access: Register or log in as a Subscriber-level user on the target WordPress site (registration may be open or credentials may be obtained through other means).
  3. Identify unprotected endpoint: Locate the plugin function or REST API/AJAX endpoint that lacks proper authorization checks — typically discoverable through source code review of the plugin's PHP files or by observing network requests in the WordPress admin area.
  4. Send crafted request: As the authenticated low-privileged user, send a direct HTTP request (e.g., a crafted AJAX or REST API call) to the vulnerable endpoint, bypassing the expected access control restrictions.
  5. Retrieve sensitive data: The server responds with restricted data (such as unpublished posts, private content, or configuration details) that should only be accessible to higher-privileged roles (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing repeated requests to plugin-specific AJAX endpoints (e.g., wp-admin/admin-ajax.php with plugin-related action parameters) from low-privileged user sessions.
  • Logs: Unusual access patterns where Subscriber-level accounts are making requests to endpoints typically reserved for Editors or Administrators.
  • Network: Automated scanning traffic targeting /wp-content/plugins/post-grid/readme.txt to fingerprint plugin version prior to exploitation attempts.
  • Logs: WordPress authentication logs showing newly registered Subscriber accounts followed immediately by API or AJAX requests to the Post Grid plugin endpoints.

Mitigation and workarounds

The primary remediation is to update the Post Grid and Gutenberg Blocks plugin to version 2.3.18 or later, which contains the fix for this vulnerability. Site administrators who cannot immediately update should consider temporarily disabling the plugin or restricting user registration to prevent unauthenticated users from obtaining the Subscriber role needed to exploit this flaw. Patchstack users benefit from a virtual patching/mitigation rule that blocks exploitation attempts until the plugin is updated (Patchstack).

Community reactions

The vulnerability was discovered and reported by security researcher Abu Hurayra and disclosed through Patchstack's coordinated vulnerability disclosure process. Patchstack classified it as medium priority and noted that broken access control vulnerabilities of this type are frequently leveraged in mass WordPress exploit campaigns. No significant broader media coverage or notable social media discussion beyond standard CVE tracking feeds has been observed (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-16955NONEN/A
  • ai-engine
NoYesAug 08, 2026
CVE-2026-16953NONEN/A
  • ai-engine
NoYesAug 08, 2026
CVE-2026-16948NONEN/A
  • solace-extra
NoYesAug 08, 2026
CVE-2026-16608NONEN/A
  • download-monitor
NoYesAug 08, 2026
CVE-2026-16595NONEN/A
  • wpdirectorykit
NoYesAug 08, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management