LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25014: WordPress Enter Addons plugin <= 2.3.2 - Cross Site Request Forgery (CSRF) vulnerability

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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25014 is a medium-severity CSRF issue in the WordPress Enter Addons plugin through version 2.3.2. If an administrator is tricked into taking an action, an attacker may cause an unintended plugin-related change. The documented impact is limited integrity impact, not data theft or service outage.

Executive priority

Treat as a routine but timely WordPress plugin risk. Prioritize internet-facing business sites and sites with many administrators. Business urgency is moderate because exploitation needs user interaction and documented impact is limited to integrity.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in themelooks Enter Addons, package enteraddons, affecting versions up to and including 2.3.2. CVSS 3.1 is 4.3: network attack vector, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites with the Enter Addons plugin installed at version 2.3.2 or earlier. Sites without this plugin are not affected based on the provided sources.

Exploitation context

The CVE requires user interaction, consistent with CSRF risk against an authenticated user such as a site administrator. The provided sources do not state active exploitation, public exploit availability, or CISA KEV listing.

Researcher notes

Public details are limited in the provided bundle. The CVE and Patchstack reference identify CSRF but do not describe the affected action, endpoint, nonce failure, exploit activity, or a specific fixed release. Avoid assuming broader impact without vendor detail.

Mitigation direction

  • Inventory WordPress sites for the Enter Addons plugin.
  • Identify any Enter Addons installations at version 2.3.2 or earlier.
  • Check vendor or Patchstack guidance for fixed versions or recommended mitigations.
  • Restrict administrative access to trusted users and networks where feasible.
  • Remind administrators not to click untrusted links while logged into WordPress.

Validation and detection

  • Confirm whether Enter Addons is installed on each WordPress site.
  • Record the installed plugin version for affected assets.
  • Compare installed versions against the affected range: through 2.3.2.
  • Review vendor and Patchstack entries for updated remediation status.
  • Check logs for unexpected plugin or settings changes by privileged users.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-25014Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
themelooksEnter Addonsenteraddons, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.