Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain subscriber-level WordPress account
-
DeliverySend crafted HTTP request to ACPT plugin endpoint
-
ExploitInject SQL metacharacters into unparameterized query parameter
-
ExecutionDatabase returns rows from arbitrary WordPress tables
-
ImpactExfiltrate user password hashes and site configuration data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid WordPress account with at minimum subscriber-level privileges, as confirmed by CVSS PR:L - unauthenticated exploitation is not supported by the vector. The ACPT (Pro) plugin must be installed and active on the target WordPress instance; the vulnerability surface does not exist without the plugin present. No other non-default configuration appears necessary beyond plugin activation and the attacker holding any authenticated session. What limits exploitation: sites with closed user registration face reduced risk because the attacker must obtain credentials through a separate means such as phishing or credential stuffing; unauthenticated access is ruled out by PR:L. All versions up to and including 2.0.63 are confirmed vulnerable. |
| Impact | The CVSS 8.5 score is well-supported by the vector: network-accessible, low complexity, no user interaction required, with Scope:Changed and high confidentiality impact. The key limiting factor is the PR:L requirement - exploitation requires at minimum a subscriber-level WordPress account, introducing at least one authentication barrier. Sites with open user registration face substantially higher exposure since any self-registered account can trigger the injection path, while closed-registration deployments require the attacker to compromise or phish credentials first. No EPSS data was supplied, preventing probabilistic exploitation comparison. The absence of a CISA KEV listing means active exploitation is unconfirmed; however, the low attack complexity and Patchstack's public disclosure mean the window before weaponization may be short. The Scope:Changed rating amplifies risk beyond typical plugin SQLi by enabling full-database reads, potentially yielding WordPress admin password hashes and site secrets. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a WordPress site running ACPT Pro 2.0.63 or earlier, or reuses any compromised low-privilege credential obtained elsewhere. The attacker crafts a malicious HTTP request to an ACPT plugin endpoint, embedding SQL metacharacters in a subscriber-controlled parameter that is passed unsanitized to a database query. The database returns rows from arbitrary WordPress tables - including wp_users - allowing the attacker to harvest password hashes and configuration secrets without triggering elevated-privilege checks. No public exploit code has been identified, but low attack complexity means rapid development is plausible following Patchstack's disclosure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
Subscriber-level SQL injection in ACPT (Pro) Custom Post Types Plugin for WordPress versions 2.0.63 and earlier permits any authenticated subscriber to extract sensitive data from the underlying WordPress database. The CVSS 8.5 score with Scope:Changed reflects that the database read extends beyond the plugin's own tables, potentially exposing WordPress user credentials, site options, and other privileged data. No public exploit code has been identified and the CVE is not listed in the CISA KEV catalog at time of analysis.
RemediationAI
The primary fix is to update ACPT (Pro) to a version beyond 2.0.63 once a patched release is confirmed by the vendor. The Patchstack advisory at https://patchstack.com/database/wordpress/plugin/advanced-custom-post-type/vulnerability/wordpress-acpt-pro-custom-post-types-plugin-for-wordpress-plugin-2-0-63-sql-injection-vulnerability?_s_id=cve should be monitored for the specific patched version number, which was not confirmed in the available intelligence. As an immediate compensating control, administrators should disable open user registration via WordPress Settings > General > uncheck 'Anyone can register', preventing unauthenticated visitors from obtaining subscriber accounts - this reduces but does not eliminate risk from existing subscriber-tier users. Deploying a WordPress-aware WAF with rules targeting SQL metacharacters in requests directed at ACPT plugin endpoints can further reduce exposure. Revoking or auditing subscriber-level accounts on sensitive sites until the patch is applied is advisable where operationally feasible.
Affected VersionsENISA
Affected Packages
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
The affected product is the ACPT (Pro) - Custom Post Types Plugin for WordPress, identified by CPE cpe:2.3:a:acpt:acpt_(pro)_-_custom_post_types_plugin_for_wordpress:*:*:*:*:*:*:*:* across all versions up to and including 2.0.63. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning subscriber-controlled input reaches a database query without parameterization or adequate escaping. In WordPress, subscriber-tier injection points are commonly found in AJAX handlers, REST API routes, or shortcode callbacks that accept user-supplied parameters and pass them directly to wpdb queries without prepared statements. The CVSS Scope:Changed metric confirms the injection can read data across table boundaries - significant in WordPress environments where a single database instance stores user accounts, authentication keys, site configuration, and plugin data, allowing an attacker to read well beyond ACPT's own tables.
Know when Wordpress Plugin 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
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Subscriber-level auth required (PR:L); no additional conditions beyond plugin active; scope changes to full database read (S:C, C:H); no confirmed write or significant availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber SQL Injection in ACPT (Pro) - Custom Post Types Plugin for WordPress <= 2.0.63 versions.
Executive ViewAI
WordPress sites using ACPT (Pro) Custom Post Types Plugin versions 2.0.63 and earlier face a critical risk: any subscriber account holder can bypass normal database security controls to extract sensitive data including login credentials and site configuration. No public exploit has been identified at time of analysis, but the lack of an available vendor patch means organizations must immediately restrict subscriber permissions or remove the plugin to prevent potential account compromise. The vulnerability window creates heightened risk for credential theft and unauthorized site access until mitigations are in place.
Restrict subscriber database query permissions at the database layer; disable the ACPT Pro plugin if not actively required; deploy Web Application Firewall rules to block SQL injection syntax targeting POST parameters; rotate all WordPress user credentials; enable comprehensive database query logging to detect exploitation attempts.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-66990
GHSA-9hrm-9f56-944v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB