dbcve.org
Ht MenuWordPress extension · Hasthemes

CVE-2023-23791

HIGH · 8.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 1.2.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in HasThemes HT Menu WordPress plugin versions 1.2.1 and below allows attackers to trick authenticated users into performing unintended administrative actions via maliciously crafted requests.

MitigationImplement anti-CSRF tokens (nonces) in all forms and AJAX endpoints within the plugin and validate these tokens server-side on every state-changing request.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ht MenuWordPress extension
Affected:< 1.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate HT Menu plugin files
    Check the WordPress plugins directory at /wp-content/plugins/ for a folder named 'ht-menu' or similar HasThemes menu plugin directory
    Affected if The plugin folder exists in the plugins directory
  2. Read the plugin version
    Open the main plugin PHP file (usually ht-menu.php or index.php) in the plugin folder and locate the 'Version' field in the plugin header comment at the top of the file
    Affected if The version number found is below 1.2.2 (for example, 1.2.1, 1.2.0, 1.1.0, etc.)
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the HasThemes HT Menu plugin shows as 'Active'
    Affected if The plugin is active and the version is below 1.2.2

If the HT Menu plugin is installed, active, and its version is 1.2.1 or lower, the environment is affected by this CSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.2 or later
Fixed in 1.2.2
Interim mitigation

Implement anti-CSRF tokens (nonces) in all forms and AJAX endpoints within the plugin and validate these tokens server-side on every state-changing request.

Recommended fix High confidence

1.2.2

  1. Log in to the WordPress admin dashboard.
  2. Navigate to Dashboard > Updates or Plugins > Installed Plugins.
  3. Locate 'HT Menu' (by HasThemes) in the list.
  4. Click 'Update Now' to install the latest version.
  5. Verify the installed version is 1.2.2 or higher after the update completes.
  6. Test the menu functionality on the frontend to ensure the plugin is working correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ht Menu Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23791 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data