LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23791: WordPress HT Menu Plugin <= 1.2.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in HasThemes HT Menu plugin <= 1.2.1 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the HasThemes HT Menu WordPress plugin through version 1.2.1. A CSRF flaw may let an attacker trick a logged-in site user into making an unintended plugin-related change. The published impact is limited to low integrity impact, with no stated confidentiality or availability impact.

Executive priority

Treat this as a routine but real WordPress hygiene item. It is not described as actively exploited and has limited impact, but exposed public WordPress sites should be inventoried and remediated during the next normal maintenance window.

Technical view

CVE-2023-23791 is a CWE-352 Cross-Site Request Forgery issue in HT Menu / ht-menu-lite <= 1.2.1. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.

Likely exposure

Exposure is limited to WordPress installations running HasThemes HT Menu, package ht-menu-lite, at version 1.2.1 or earlier. Sites not using this plugin, or using unaffected versions, are not indicated as exposed by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Because this is CSRF, practical abuse depends on convincing a legitimate logged-in user to interact with malicious content while authenticated.

Researcher notes

The public data is sparse: it names CSRF, affected plugin, version boundary, CWE, CVSS, and Patchstack reference, but not the exact vulnerable action, nonce failure details, or fixed version. Avoid asserting exploitability beyond user-assisted CSRF with low integrity impact.

Mitigation direction

  • Inventory WordPress sites for HT Menu or ht-menu-lite installations.
  • Check HasThemes and Patchstack guidance for the fixed or unaffected version.
  • Upgrade away from affected versions when vendor guidance identifies a safe release.
  • If no safe upgrade is available, consider disabling the plugin until reviewed.
  • Restrict administrative sessions and reinforce anti-phishing controls for WordPress users.

Validation and detection

  • Confirm whether HT Menu / ht-menu-lite is installed on each WordPress site.
  • Record installed plugin versions and compare against <= 1.2.1 exposure.
  • Review WordPress admin audit logs for unexpected plugin configuration changes.
  • Check whether vendor or Patchstack advisories list a corrected version.
  • Verify compensating controls do not rely on user vigilance alone.
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-23791 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-23791Attack 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 Menuht-menu-lite, 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.