dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-13412

HIGH · 7.5 CVSS v3.1 Published 2025-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 CozyStay theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the ajax_handler function in all versions up to, and including, 1.7.0. This makes it possible for unauthenticated attackers to execute arbitrary actions.

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 CozyStay WordPress theme has a broken access control vulnerability in its ajax_handler function. The function lacks proper capability checks, allowing any unauthenticated user to invoke it and execute arbitrary actions due to missing authorization validation.

MitigationAdd proper WordPress capability checks (e.g., current_user_can()) to the ajax_handler function to ensure only authorized users can execute the actions, or update to a patched version if available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify if CozyStay theme is installed
    In WordPress admin, go to Appearance > Themes to see if CozyStay is installed and active. Alternatively, check the /wp-content/themes/ directory for a folder named 'cozystay' or similar.
    Affected if CozyStay theme is present and active in the WordPress installation
  2. Locate the ajax_handler function
    Search the theme files for 'ajax_handler' function definition, typically in functions.php or includes/ajax.php files within the CozyStay theme folder.
    Affected if The ajax_handler function exists in the theme code
  3. Check for capability validation in ajax_handler
    Open the ajax_handler function file and inspect its code for WordPress capability checks like 'current_user_can()' or 'wp_verify_nonce()' at the function entry point.
    Affected if No capability check (current_user_can) or nonce validation is found at the beginning of the ajax_handler function
  4. Verify AJAX endpoint accessibility
    Check the WordPress admin AJAX endpoint (wp-admin/admin-ajax.php) for hooks registering the CozyStay theme's ajax actions (look for 'cozystay' or theme-specific action names in add_action('wp_ajax_...') calls).
    Affected if AJAX actions are registered and accessible without requiring authentication

The environment is affected if the CozyStay theme is installed and the ajax_handler function lacks proper capability checks (current_user_can) and nonce validation, allowing unauthenticated access to execute arbitrary actions.

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

Add proper WordPress capability checks (e.g., current_user_can()) to the ajax_handler function to ensure only authorized users can execute the actions, or update to a patched version if available.

Recommended fix Moderate confidence

CozyStay theme version higher than 1.7.0 (e.g., 1.7.1 or latest available)

  1. Obtain the latest version of the CozyStay theme from a trusted source such as ThemeForest or the theme developer's official website
  2. Log in to the WordPress admin dashboard
  3. Navigate to Appearance > Themes
  4. Deactivate and delete the current CozyStay theme version
  5. Install and activate the updated CozyStay theme version (version higher than 1.7.0)
  6. Verify that the ajax_handler function now includes proper capability checks by reviewing theme changelog or release notes
  7. Test that theme functionality works as expected after the update
Caveat Minor or patch updates typically have no breaking changes; review theme changelog for any compatibility notes with WordPress version or installed plugins

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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