CVE-2025-12125
BaseFortify
Publication date: 2025-11-08
Last updated on: 2025-11-12
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpres | html_forms_plugin | 1.5.5 |
| wordpres | html_forms_plugin | 1.5.6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the HTML Forms – Simple WordPress Forms Plugin for WordPress, affecting all versions up to and including 1.5.5. It occurs because the plugin does not properly sanitize input or escape output in admin settings. As a result, an authenticated attacker with administrator-level permissions or higher can inject malicious scripts into pages. These scripts execute whenever a user accesses the infected page. The vulnerability specifically affects multi-site installations and installations where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with administrator-level access to inject malicious scripts that execute in the context of users visiting the affected pages. This can lead to unauthorized actions, data theft, session hijacking, or other malicious activities performed on behalf of users without their consent. Since it requires high privileges and affects multi-site or restricted HTML filtering environments, the impact is limited but can still compromise site integrity and user security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the HTML Forms – Simple WordPress Forms Plugin to a version later than 1.5.5 where the issue is fixed. Additionally, ensure that only trusted administrators have access to the plugin settings, and consider enabling unfiltered_html if possible, or review multisite configurations carefully to limit exposure.