dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-52388

HIGH · 7.1 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 mikeage Hebrew Date hebrewdates allows Stored XSS.This issue affects Hebrew Date: from n/a through <= 2.1.0.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Hebrew Date WordPress plugin (hebrewdates) allows attackers to trick authenticated administrators into submitting malicious requests that result in Stored XSS. The lack of CSRF protection enables the injection of persistent malicious scripts through plugin forms.

MitigationUpdate the Hebrew Date plugin to the latest patched version. If no update is available, implement anti-CSRF tokens (nonces) on all plugin form submissions and ensure proper input sanitization to prevent XSS.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Hebrew Date plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and search for 'Hebrew Date' or 'hebrewdates'. Confirm the plugin is installed and activated.
    Affected if The Hebrew Date plugin (hebrewdates) is installed and active on the WordPress site.
  2. Check installed plugin version
    In the Plugins list, locate the Hebrew Date plugin and note the version number displayed. Compare this to the version that contains the patch for CVE-2024-52388.
    Affected if The installed version is older than the patched version that addresses CSRF protection.
  3. Inspect plugin forms for nonce fields
    Access the plugin source code in wp-content/plugins/hebrewdates/. Search form handlers for the presence of wp_nonce_field() or check_admin_referer() calls. Examine all plugin settings and submission forms.
    Affected if Plugin forms lack CSRF nonce tokens (wp_nonce_field) or nonce verification (check_admin_referer) in form handling code.
  4. Check for XSS-susceptible input handling
    In the plugin source code, examine functions that process form submissions or user input. Look for missing sanitization functions like esc_html(), esc_attr(), or sanitize_text_field() on input that gets stored or displayed.
    Affected if Plugin stores or displays user input without proper sanitization, allowing stored XSS to occur.

A user is affected if the Hebrew Date plugin is installed, the version lacks CSRF protection (missing nonce verification), and plugin forms can be leveraged for stored XSS through forged admin requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Hebrew Date plugin to the latest patched version. If no update is available, implement anti-CSRF tokens (nonces) on all plugin form submissions and ensure proper input sanitization to prevent XSS.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (newer than 2.1.0)

  1. 1. Update the Hebrew Date plugin (mikeage) to the latest available version from the WordPress plugin repository
  2. 2. After updating, verify that the plugin's admin forms and user-facing features include anti-CSRF tokens (nonces)
  3. 3. Clear all site caches and test the plugin functionality to confirm the update was successful
  4. 4. If a fixed version is not yet available in the WordPress repository, contact the plugin developer (mikeage) for a patched release

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

Have this fixed 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 help mitigating

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-2024-52388 — 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-52388 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