CVE-2025-58262
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-22

Last updated on: 2026-04-23

Assigner: Patchstack

Description
Cross-Site Request Forgery (CSRF) vulnerability in WPDirectoryKit Sweet Energy Efficiency sweet-energy-efficiency allows Stored XSS.This issue affects Sweet Energy Efficiency: from n/a through <= 1.0.8.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-22
Last Modified
2026-04-23
Generated
2026-05-27
AI Q&A
2025-09-22
EPSS Evaluated
2026-05-25
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordpress sweet_energy_efficiency 1.0.6
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-58262 is a Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Sweet Energy Efficiency Plugin (versions up to 1.0.6). It allows a malicious actor to trick authenticated users with higher privileges into performing unwanted actions on the site, potentially compromising site integrity. This vulnerability is related to broken access control and can lead to stored cross-site scripting (XSS) issues. [1]


How can this vulnerability impact me? :

This vulnerability can impact you by allowing attackers to execute unauthorized actions on your WordPress site when a privileged user is tricked into performing them. This can compromise the integrity of your site, potentially leading to stored XSS attacks and other malicious activities. Although the severity is considered low and exploitation is unlikely, it still poses a risk to site security. [1]


What immediate steps should I take to mitigate this vulnerability?

Since no official fix or patched version is currently available, immediate mitigation steps include monitoring for updates from the plugin developer and applying virtual patching (vPatching) solutions as recommended by Patchstack to reduce risk. Additionally, consider limiting user privileges and educating users about the risks of executing untrusted actions while authenticated to help mitigate exploitation. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart