CVE-2026-18030
Bricksforge < 3.1.8.8 - Unauthenticated Arbitrary Password Reset via Pro Forms
Description
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.
INFO
Published Date :
Aug. 10, 2026, 7:16 a.m.
Last Modified :
Aug. 10, 2026, 7:16 a.m.
Remotely Exploit :
No
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-18030
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the BricksForge WordPress plugin.
- Verify the current-password verification option is enabled.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-18030.
| URL | Resource |
|---|---|
| https://wpscan.com/vulnerability/15463bda-fb39-4629-b96b-34b83191bab7/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-18030 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-18030
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-18030 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-18030 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Aug. 10, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'Unknown', 'product': 'BricksForge', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '3.1.8.8', 'versionType': 'semver'}], 'defaultStatus': 'unaffected'}] Added Description 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. Added Reference https://wpscan.com/vulnerability/15463bda-fb39-4629-b96b-34b83191bab7/