dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10673

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 Top Store theme for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the top_store_install_and_activate_callback() function in all versions up to, and including, 1.5.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to install arbitrary plugins which can contain other exploitable vulnerabilities to elevate privileges and gain remote code execution.

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 Top Store WordPress theme fails to validate user capabilities before executing the top_store_install_and_activate_callback() function, allowing any authenticated user with subscriber-level permissions to install and activate arbitrary plugins. This can be chained with malicious plugins to achieve privilege escalation and remote code execution.

MitigationUpdate the Top Store theme to version 1.5.5 or later which includes proper capability checks. If immediate update is not feasible, disable or remove the vulnerable function and monitor for unauthorized plugin installations.

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. Confirm Top Store theme is installed
    Navigate to Appearance > Themes in the WordPress admin dashboard and look for the Top Store theme. Note whether it is the currently active theme.
    Affected if The Top Store theme is installed and active on the WordPress site.
  2. Check the Top Store theme version
    In the Themes admin page, click on the Top Store theme to view its details. The version number is displayed there. Alternatively, inspect the style.css file in the theme directory and look for the 'Version:' header comment.
    Affected if The installed version is lower than 1.5.5 (the patched version).
  3. Verify the vulnerable callback function exists
    Access the WordPress site via FTP or file manager and locate the theme files, typically in /wp-content/themes/top-store/. Search for the function named 'top_store_install_and_activate_callback' within the theme PHP files, particularly in any file related to plugin installation or AJAX handlers.
    Affected if The function 'top_store_install_and_activate_callback' exists in the theme files and lacks a capability check (the function should verify administrator-level privileges but the vulnerability exists when it does not).
  4. Review user accounts for unauthorized access
    Navigate to Users > All Users in the WordPress admin panel. Examine the roles assigned to all users. Check if any users have subscriber-level or higher access who should not have such access. Additionally, review the list of installed and activated plugins for any that were installed without proper authorization.
    Affected if There are user accounts with subscriber-level access (or higher) that were not intentionally created, or if plugins appear in the list that were installed by non-administrator users.

The site is affected if the Top Store theme is installed (especially if active) at a version lower than 1.5.5, the vulnerable function exists without capability checks, or non-administrator accounts have installed 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 Top Store theme to version 1.5.5 or later which includes proper capability checks. If immediate update is not feasible, disable or remove the vulnerable function and monitor for unauthorized plugin installations.

Recommended fix Moderate confidence

Latest version of Top Store theme (version higher than 1.5.4)

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Appearance > Themes.
  3. 3. Check the current version of the Top Store theme installed.
  4. 4. If a newer version than 1.5.4 is available in the WordPress theme repository, update to that version.
  5. 5. Alternatively, download the latest version of the Top Store theme from the official WordPress theme repository and upload it via Appearance > Themes > Add New > Upload Theme.
  6. 6. After updating, verify the version number reflects the update.
  7. 7. Review user roles on the site to ensure no unauthorized subscriber accounts were created.
Caveat Theme updates may require reconfiguration of custom settings; backup the site before updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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