CVE-2025-12631
BaseFortify
Publication date: 2025-11-11
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 |
|---|---|---|
| tony_destefano | plugin_squirrels_auto_inventory | 1.0.3 |
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 Squirrels Auto Inventory plugin for WordPress, affecting versions up to and including 1.0.3. It occurs because the plugin does not properly sanitize input or escape output in the admin settings. As a result, authenticated users with administrator-level permissions or higher can inject malicious scripts that execute whenever a user views the affected page. This vulnerability specifically impacts multi-site installations and those where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
The vulnerability allows attackers with administrator-level access to inject malicious scripts into the website, which will execute in the browsers of users who visit the infected pages. This can lead to unauthorized actions such as stealing session tokens, defacing the website, or performing actions on behalf of other users. Since it requires high-level permissions and affects multi-site or restricted HTML installations, the impact is limited but can still compromise site integrity and user trust.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Squirrels Auto Inventory plugin for WordPress to a version later than 1.0.3 where the issue is fixed. Additionally, ensure that only trusted administrators have access to the plugin settings, and consider enabling unfiltered_html if appropriate, or review multi-site installations carefully since the vulnerability affects only multi-site setups or those with unfiltered_html disabled.