dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12202

HIGH · 8.8 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Croma Music plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'ironMusic_ajax' function in all versions up to, and including, 3.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 Croma Music WordPress plugin has a broken access control vulnerability in the ironMusic_ajax function. The AJAX handler lacks capability checks, allowing any authenticated user with Subscriber-level access to modify arbitrary WordPress options. This can be exploited by changing the default_user_role to Administrator and enabling user_registration to create an admin account.

MitigationUpdate Croma Music plugin to version 3.7 or later which includes proper capability checks. Until patched, disable the plugin or restrict site registration.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Croma Music plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Croma Music' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active, and its version is earlier than 3.7.
  2. Check the installed plugin version
    Click on the Croma Music plugin in the plugins list to view its details, or inspect the plugin header in /wp-content/plugins/croma-music/ directory to read the Version field.
    Affected if The version displayed is before 3.7 (the version with the security fix).
  3. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and locate the 'Membership' setting. Check if 'Anyone can register' is enabled.
    Affected if User registration is enabled on the site while the vulnerable plugin version is active.
  4. Inspect the default user role setting
    In WordPress admin, go to Settings > General and check the 'Default Role' dropdown. Alternatively, query the 'default_role' option in the wp_options table.
    Affected if The default role is set to Administrator.
  5. Verify low-privilege user access to AJAX handler
    Test whether an authenticated user with Subscriber role can access the wp-admin/admin-ajax.php?action=ironMusic_ajax endpoint. Submit a request modifying a WordPress option (such as default_user_role) using the AJAX function.
    Affected if The AJAX handler responds to requests from Subscriber-level users without returning a capability error.

You are affected if Croma Music plugin versions before 3.7 are active on your site and user registration is enabled, allowing any subscriber-level user to modify WordPress options via the ironMusic_ajax function.

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 Croma Music plugin to version 3.7 or later which includes proper capability checks. Until patched, disable the plugin or restrict site registration.

Recommended fix Moderate confidence

Latest version after 3.6 (check WordPress plugin repository for 3.7 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Croma Music plugin
  4. 4. Check the current installed version (should be 3.6 or below if vulnerable)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Alternatively, download the latest version from the WordPress plugin repository or the official Croma website
  7. 7. Deactivate and delete the old plugin version if automatic update doesn't work, then install the new version
  8. 8. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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