dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10674

HIGH · 8.8 CVSS v3.1 Published 2024-11-09
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 Th Shop Mania theme for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the th_shop_mania_install_and_activate_callback() function in all versions up to, and including, 1.4.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install arbitrary plugins which can be leveraged to exploit other vulnerabilities and achieve remote code execution and privilege escalation.

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 Th Shop Mania WordPress theme (versions up to 1.4.9) contains a broken access control vulnerability in the th_shop_mania_install_and_activate_callback() function which lacks a proper capability check. This allows any authenticated user with Subscriber-level permissions or higher to install and activate arbitrary WordPress plugins from the repository, enabling privilege escalation to admin-level access and potential remote code execution.

MitigationUpdate the theme to version 1.4.10 or later which includes the proper capability check; alternatively, add a capability check (require 'manage_options') to the callback function or remove/disable the plugin installation functionality entirely.

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. Identify the installed Th Shop Mania theme version
    In WordPress admin, go to Appearance > Themes and check the version listed for Th Shop Mania theme, or inspect the theme's style.css file for the Version header
    Affected if The version is 1.4.9 or lower (any version up to and including 1.4.9 is vulnerable)
  2. Verify the presence of the vulnerable callback function
    Inspect theme files (typically in functions.php or includes folder) for the function named th_shop_mania_install_and_activate_callback
    Affected if This function exists in the theme code without a proper capability check before it
  3. Check user role assignments on the site
    In WordPress admin, go to Users and review the role assigned to each user account
    Affected if Any user account exists with Subscriber role or higher (Contributor, Author, Editor, Admin) since the vulnerability affects any authenticated user with at least Subscriber-level access
  4. Review recently activated plugins for anomalies
    In WordPress admin, go to Plugins and check for any unfamiliar or recently installed plugins that were not explicitly installed by administrators
    Affected if Unknown plugins appear activated that were not intentionally installed by legitimate administrators, indicating potential exploitation

A site is affected if it runs Th Shop Mania theme version 1.4.9 or lower AND has at least one user account with Subscriber-level permissions or higher, since the vulnerable function can be invoked by any authenticated user to install/activate arbitrary plugins.

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 theme to version 1.4.10 or later which includes the proper capability check; alternatively, add a capability check (require 'manage_options') to the callback function or remove/disable the plugin installation functionality entirely.

Recommended fix Moderate confidence

Version higher than 1.4.9 (check wordpress.org/themes for latest stable release)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the 'Th Shop Mania' theme
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version of the Th Shop Mania theme from a trusted source (wordpress.org/themes or the theme developer's site)
  6. 6. Go to Themes > Add New > Upload Theme
  7. 7. Upload and install the updated theme file
  8. 8. Activate the new theme version
Caveat Check theme changelog for potential template/feature changes before upgrading on production sites

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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