ZoxpressWordPress extension · Mvpthemes
CVE-2024-13654
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 · uneditedThe ZoxPress - The All-In-One WordPress News Theme theme for WordPress is vulnerable to unauthorized modification of data that can lead to a denial of service due to a missing capability check on the 'reset_options' function in all versions up to, and including, 2.12.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary option values on the WordPress site. This can be leveraged to delete an option that would create an error on the site and deny service to legitimate users.
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 confidenceThe ZoxPress WordPress theme lacks a capability check on its 'reset_options' function, allowing any authenticated user with Subscriber-level permissions to delete arbitrary WordPress database options. This can be exploited to remove critical options (like siteurl or active_plugins), causing fatal errors and denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ZoxpressWordPress extension
< 2.12.1CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zoxpress theme versionCheck the style.css file in wp-content/themes/zoxpress/ for the Version: header, or query the WordPress options table for the theme version if stored thereAffected if Installed version is below 2.12.1
-
Locate the reset_options functionSearch the theme files (typically functions.php or includes/admin files) for the function named 'reset_options' or similar patterns like 'reset_options_'Affected if The function exists and is accessible via an AJAX hook or admin URL without capability checks
-
Verify the function lacks capability checksExamine the reset_options function code - look for 'current_user_can', 'manage_options', or similar permission checks at the function entry pointAffected if No capability check (or only a weak check like 'edit_posts') is present before the option deletion logic
-
Confirm subscriber-level users existCheck WordPress users table or user management to see if accounts with the Subscriber role existAffected if Any Subscriber-level accounts are present in the system
-
Test if the vulnerable endpoint is reachableIf the theme exposes an AJAX action (like wp_ajax_zoxpress_reset_options), attempt a request with a subscriber-level auth cookie or check the theme's admin init hooks for unregistered endpointsAffected if The reset_options function can be triggered without elevated permissions
If the Zoxpress theme version is below 2.12.1 and the reset_options function lacks a 'manage_options' capability check, any authenticated Subscriber user can delete critical WordPress options.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.12.1
Update to a patched version of the theme once released, or add a capability check (e.g., 'manage_options') to the reset_options function to restrict access to administrators only.
Upgrade to ZoxPress theme version 2.12.1
- Log in to the WordPress admin dashboard
- Navigate to Appearance > Themes
- Find the ZoxPress theme and click on it to view details
- Click the 'Update Now' button to upgrade to version 2.12.1
- Alternatively, download version 2.12.1 from themeforest.net and upload it via Appearance > Themes > Add New > Upload Theme
- Verify the update was successful by confirming the version shows 2.12.1
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Zoxpress
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-13654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13654 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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