Sweet Energy Efficiency <= 1.0.6 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Graph Deletion
Strategic Overview
- Status
- Patched in 1.0.7
- Affected Plugin
- Sweet Energy Efficiency
- Affected Version
<= 1.0.6- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-14618
At a glance
CVE-2025-14618 is a medium-severity Missing Authorization vulnerability in the Sweet Energy Efficiency WordPress plugin, affecting versions <= 1.0.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.0.7; sites on affected versions should update now. Disclosed December 2025, reported by Paolo Tresso.
Vulnerability Overview
The Sweet Energy Efficiency plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to a missing capability check on the 'sweet_energy_efficiency_action' AJAX handler in all versions up to, and including, 1.0.6. This makes it possible for authenticated attackers, with subscriber level access and above, to read, modify, and delete arbitrary graphs.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Sweet Energy Efficiency <= 1.0.6 carries this weakness at sweet_energy_efficiency_action, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Sweet Energy Efficiency the fix is 1.0.7: builds <= 1.0.6 are affected, anything from 1.0.7 onward is not.
Remediation
Update to version 1.0.7, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Sweet Energy Efficiency 1.0.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Sweet Energy Efficiency
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C