CVE-2025-12371
BaseFortify
Publication date: 2025-11-04
Last updated on: 2025-11-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | nari_accountant_plugin | 1.0.12 |
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 Nari Accountant plugin for WordPress, affecting versions up to 1.0.12. It occurs because the plugin does not properly sanitize input or escape output in account settings. Authenticated users with editor-level permissions or higher can inject malicious scripts that execute when other users view the affected pages. This vulnerability only affects multi-site WordPress installations or those where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
The vulnerability allows attackers with certain permissions to inject malicious scripts that run in other users' browsers when they visit the compromised pages. This can lead to unauthorized actions, data theft, session hijacking, or other malicious activities within the affected WordPress site. The impact is limited to multi-site installations or those with unfiltered_html disabled and requires editor-level or higher permissions to exploit.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update the Nari Accountant plugin to a version later than 1.0.12 where the issue is fixed. Additionally, ensure that only trusted users have editor-level or higher permissions, especially in multi-site WordPress installations. If possible, review and adjust the 'unfiltered_html' setting to limit the ability to inject scripts. Monitoring and restricting user permissions can reduce the risk of exploitation.