ACPT (Premium) <= 2.0.66 - Unauthenticated Privilege Escalation via 'acpt_form_post_id' Parameter
Strategic Overview
- Status
- Patched in 2.0.67
- Affected Plugin
- ACPT (Premium)
- Affected Version
<= 2.0.66- CVSS
- 9.8Critical
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-15354
At a glance
CVE-2026-15354 is a critical-severity Improper Privilege Management vulnerability in the ACPT (Premium) WordPress plugin, affecting versions <= 2.0.66. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.67; sites on affected versions should update now. Disclosed September 2026, reported by d.v4n_s3c.
Vulnerability Overview
The ACPT (Premium) plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.0.66. This is due to missing authorization in the `submit()` function, which allows unauthenticated form submissions to control the target user ID before calling `wp_update_user()`. This makes it possible for unauthenticated attackers to overwrite any WordPress user's email address and password, including an administrator's, and take over the account. Successful exploitation requires a public ACPT user form that permits anonymous submissions.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
ACPT (Premium) <= 2.0.66 carries this weakness at submit(), and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For ACPT (Premium) the fix is 2.0.67: builds <= 2.0.66 are affected, anything from 2.0.67 onward is not.
Remediation
Update to version 2.0.67, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: ACPT (Premium) 2.0.67 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in ACPT (Premium)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C