ResetWordPress extension · Smartzminds
CVE-2024-13684
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 Reset plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6. This is due to missing or incorrect nonce validation on the reset_db_page() function. This makes it possible for unauthenticated attackers to reset several tables in the database like comments, themes, plugins, and more via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 Reset WordPress plugin has a CSRF vulnerability in the reset_db_page() function due to missing nonce validation. Unauthenticated attackers can forge requests that reset database tables (comments, themes, plugins, etc.) by tricking administrators into clicking malicious links.
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
ResetWordPress extension
<= 1.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify Reset plugin is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for a 'reset' folder from SmartzmindsAffected if The Smartzminds Reset plugin appears in the installed plugins list
-
Check installed plugin versionIn WordPress admin, view plugin details for Reset plugin to see the version number, or read the main plugin PHP file header which contains the Version fieldAffected if The displayed version is 1.6 or any version lower than 1.6
-
Identify vulnerable function in plugin codeAccess the plugin files via file manager or FTP, locate the file containing reset_db_page() function, and inspect the function for missing wp_verify_nonce() or check_admin_referer() callsAffected if The reset_db_page() function exists and lacks nonce validation checks before performing database operations
-
Confirm admin access is requiredUnderstand that this CSRF attack requires a logged-in administrator to trigger the malicious request, so verify if any administrator-level users exist on the siteAffected if The site has active administrator accounts who could be tricked into clicking a forged request URL
A site is affected if the Smartzminds Reset plugin version 1.6 or lower is installed and the plugin's reset_db_page() function lacks nonce validation, with the attack requiring a logged-in administrator to trigger the forged request.
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.
From vendor dataUpdate the Reset plugin beyond version 1.6 when a patched version is released; temporarily disable the plugin if no update is available.
Fix this in Reset
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13684 — 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-13684 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