CVE-2026-18030
HighCVSS 8.1Exploitation Probability (EPSS)
Low risk20th percentile - higher than 20% of all known CVEs
Summary
The BricksForge WordPress plugin before version 3.1.8.8 does not verify the identity of the requester when processing a password change submitted through one of its form actions. This allows unauthenticated attackers to set an arbitrary password for any user, including administrators, and take over their account. Exploitation requires the site to have a form using the password reset action in update mode; the server-side current-password verification is disabled by default, so the vulnerable state is the default once the action is used.
Risk Assessment
An unauthenticated attacker can take over an administrator account, leading to full site compromise.
Recommendation
Update the BricksForge plugin to version 3.1.8.8 or later, which includes fixes for identity verification and enables current-password verification by default.
Other vulnerabilities in BricksForge
See all- CVE-2026-34888High
Versions of Bricksforge <= 3.1.8.4 have a vulnerability that allows unauthorized access to sensitive data.
- CVE-2026-14956Critical
The Bricksforge plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.1.8.6. This is due to improper validation of the fieldIds parameter in the Pro Forms registration action, which allows attacker-supplied field IDs to be added to the trusted form-field whitelist. This makes it possible for unauthenticated attackers to register a new administrator account by submitting a crafted request to a publicly accessible Bricksforge Pro Forms registration form.
Original NVD description (English source)
The BricksForge WordPress plugin before 3.1.8.8 does not verify the identity of the requester when processing a password change submitted through one of its form actions, allowing unauthenticated attackers to set an arbitrary password for any user, including administrators, and take over their account. Exploitation requires the site to have a form using the BricksForge WordPress plugin before 3.1.8.8's password reset action in its update mode. The server-side current-password verification option for that action is disabled by default, so the vulnerable state is the default one once the action is used.