LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51529: WordPress HT Mega Plugin <= 2.3.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in HasThemes HT Mega – Absolute Addons For Elementor.This issue affects HT Mega – Absolute Addons For Elementor: from n/a through 2.3.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51529 affects the WordPress HT Mega - Absolute Addons For Elementor plugin through version 2.3.3. It is a CSRF issue, meaning a logged-in user could be tricked into making an unintended low-impact change. The published severity is medium, with limited integrity impact and no stated data theft or outage impact.

Executive priority

Treat this as a routine but real WordPress plugin risk. It is not currently supported by KEV or active exploitation evidence, but exposed internet-facing WordPress sites should be inventoried and remediated through normal vulnerability management timelines.

Technical view

The CVE describes CWE-352 cross-site request forgery in HasThemes HT Mega - Absolute Addons For Elementor, package ht-mega-for-elementor, affecting versions through 2.3.3. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required by attacker, user interaction required, low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites that have HT Mega - Absolute Addons For Elementor installed at version 2.3.3 or earlier. The bundle does not identify affected endpoints, specific actions, or whether default configurations are exposed.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires user interaction, consistent with CSRF risk, but the bundle does not provide public exploit evidence or operational details.

Researcher notes

Evidence is incomplete for endpoint-level validation: the bundle names CSRF, affected product, version range, CWE, and CVSS, but not the vulnerable action, nonce behavior, fixed version, or exploit status. Keep analysis constrained to version exposure and vendor advisory confirmation.

Mitigation direction

  • Inventory WordPress sites for ht-mega-for-elementor installations.
  • Confirm whether installed versions are 2.3.3 or earlier.
  • Check HasThemes or Patchstack guidance for the fixed version or official mitigation.
  • Upgrade to a vendor-supported fixed release if vendor guidance identifies one.
  • Temporarily disable the plugin where exposure is confirmed and no fix is available.
  • Limit WordPress administrative access to trusted users and managed browsers.

Validation and detection

  • Record plugin name, package slug, and installed version for each WordPress site.
  • Flag any HT Mega installation at version 2.3.3 or earlier.
  • Review vendor advisory status before asserting a patched version.
  • Check WordPress administrative change logs for unexpected plugin setting changes.
  • Document remediation status and any temporary disablement decisions.
Prepared
Confidence
medium
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-2023-51529 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-2023-51529Attack 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
HasThemesHT Mega – Absolute Addons For Elementorht-mega-for-elementor, n/aunaffected
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.