CVE-2026-25014
Unknown Unknown - Not Provided
Cross-Site Request Forgery in Enter Addons

Publication date: 2026-02-03

Last updated on: 2026-02-03

Assigner: Patchstack

Description
Cross-Site Request Forgery (CSRF) vulnerability in themelooks Enter Addons enteraddons allows Cross Site Request Forgery.This issue affects Enter Addons: from n/a through <= 2.3.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-03
Last Modified
2026-02-03
Generated
2026-05-07
AI Q&A
2026-02-03
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
themelooks enter_addons to 2.3.2 (inc)
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-2026-25014 is a Cross Site Request Forgery (CSRF) vulnerability affecting the WordPress Enter Addons Plugin versions up to and including 2.3.2.

This vulnerability allows an attacker to trick privileged users into executing unwanted actions while authenticated, by having them click a malicious link, visit a crafted page, or submit a form.

The exploit requires user interaction and a privileged user role, but no authentication is needed for the attacker to initiate the attack.

It is classified under OWASP Top 10 A1: Broken Access Control and has a CVSS score of 4.3, indicating low severity and low priority.


How can this vulnerability impact me? :

This vulnerability can impact you by allowing an attacker to perform unauthorized actions on your WordPress site if you have the Enter Addons Plugin version 2.3.2 or earlier and you have a privileged user role.

An attacker can trick you into executing actions you did not intend by making you click a malicious link, visit a crafted page, or submit a form while you are authenticated.

Although the severity is low and the threat is unlikely to be widely exploited, it can still lead to unwanted changes or actions on your site.

Updating to version 2.3.3 or later is recommended to mitigate this risk.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability affects the WordPress Enter Addons Plugin versions up to and including 2.3.2. Detection involves identifying if this plugin and vulnerable version is installed on your WordPress site.'}, {'type': 'paragraph', 'content': 'You can check the installed plugin version by accessing your WordPress admin dashboard or by running commands on your server to list the plugin versions.'}, {'type': 'list_item', 'content': 'Use WP-CLI command to check the plugin version: wp plugin list --status=active'}, {'type': 'list_item', 'content': "Look specifically for 'enteraddons' plugin and verify if its version is 2.3.2 or lower."}, {'type': 'list_item', 'content': "Alternatively, check the plugin version by inspecting the plugin's main PHP file in the WordPress plugins directory, e.g., cat wp-content/plugins/enteraddons/enteraddons.php | grep 'Version'"}] [1]


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to update the Enter Addons Plugin to version 2.3.3 or later, where this CSRF vulnerability has been patched.

If immediate updating is not possible, consider disabling the plugin temporarily to prevent exploitation.

Additionally, ensure that privileged users are cautious about clicking unknown links or visiting untrusted pages while authenticated.

Using security tools or plugins that provide auto-updates or vulnerability mitigation can also help reduce risk.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided information does not specify any direct impact of this Cross-Site Request Forgery (CSRF) vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.


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