dbcve.org
Hash ElementsWordPress extension · Hashthemes

CVE-2024-10802

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 1.4.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The Hash Elements plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the hash_elements_get_posts_title_by_id() function in all versions up to, and including, 1.4.7. This makes it possible for unauthenticated attackers to retrieve draft post titles that should not be accessible to unauthenticated users.

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 · high confidence

The Hash Elements WordPress plugin has a broken access control vulnerability in the hash_elements_get_posts_title_by_id() function, which lacks a capability check. This allows unauthenticated attackers to query the function and retrieve titles of draft posts that should only be accessible to authorized users.

MitigationUpdate Hash Elements plugin to version 1.4.8 or later, which includes the missing capability check. Until updated, consider restricting access to the affected endpoint or disabling the plugin if immediate update is not possible.

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
Hash ElementsWordPress extension
Affected:< 1.4.8

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Verify Hash Elements plugin is installed
    Check if the Hash Elements plugin is installed on your WordPress site. In WordPress admin, go to Plugins > Installed Plugins and look for 'Hash Elements' by Hashthemes. Alternatively, inspect the wp-content/plugins/ directory for a hash-elements folder.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In WordPress admin Plugins list, click on the plugin name to view details and find the version number. Compare this against the affected range: versions prior to 1.4.8 are vulnerable.
    Affected if Installed version is lower than 1.4.8
  3. Identify the vulnerable function endpoint
    Inspect the plugin files (typically in hash-elements/includes/ or similar) for the function hash_elements_get_posts_title_by_id and locate the AJAX action hook (wp_ajax_ or wp_ajax_nopriv_) that calls it. Note the associated AJAX endpoint (usually admin-ajax.php with action parameter).
    Affected if The function exists and is hooked to an AJAX action accessible to unauthenticated users (wp_ajax_nopriv_)
  4. Test unauthenticated access to the vulnerable function
    Send a crafted request to your site's wp-admin/admin-ajax.php endpoint with the action parameter matching the vulnerable AJAX action (e.g., ?action=hash_elements_get_posts_title_by_id). Include a post ID parameter to query a draft post. No authentication cookies should be sent.
    Affected if The request returns a draft post title without requiring authentication or capability verification

Your environment is affected if the Hash Elements plugin is installed with a version lower than 1.4.8 AND the vulnerable AJAX endpoint responds to unauthenticated requests by returning draft post titles.

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.4.8 or later
Fixed in 1.4.8
Interim mitigation

Update Hash Elements plugin to version 1.4.8 or later, which includes the missing capability check. Until updated, consider restricting access to the affected endpoint or disabling the plugin if immediate update is not possible.

Recommended fix High confidence

Hash Elements version 1.4.8

  1. Update the Hash Elements plugin to version 1.4.8 or later via the WordPress plugin repository, or download the latest version from the official WordPress plugin directory

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

Fix this in Hash Elements Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10802 — 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-2024-10802 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