dbcve.org
DigitsWordPress extension · Unitedover

CVE-2024-0203

HIGH · 8.8 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to after 8.4.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Digits plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 8.4.1. This is due to missing nonce validation in the 'digits_save_settings' function. This makes it possible for unauthenticated attackers to modify the default role of registered users to elevate user privileges 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 confidence

The Digits WordPress plugin lacks nonce validation in its 'digits_save_settings' function, allowing unauthenticated attackers to craft forged requests that modify plugin settings. Specifically, attackers can change the default user registration role to an elevated privilege level by tricking administrators into clicking a malicious link, achieving privilege escalation without authentication.

MitigationUpgrade the Digits plugin to version 8.4.2 or later which includes proper nonce validation. As an interim measure, advise administrators not to click untrusted links, but this does not adequately mitigate the vulnerability.

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
DigitsWordPress extension
Affected:<= 8.4.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Digits plugin is installed
    Navigate to WordPress admin > Plugins and check if the 'Digits' or 'Unitedover Digits' plugin is listed and active, or check the /wp-content/plugins/digits directory exists on the server
    Affected if The Digits plugin is present and active in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin > Plugins, find the Digits plugin and note the version number displayed, or inspect the main plugin file (e.g., digits.php) and look for the 'Version:' header comment
    Affected if The installed version is 8.4.2 or lower
  3. Verify the vulnerable function exists
    Inspect the Digits plugin files, specifically searching for the 'digits_save_settings' function in the plugin source code to confirm it lacks nonce validation logic
    Affected if The 'digits_save_settings' function exists and does not contain nonce verification (look for 'check_admin_referer' or 'wp_verify_nonce' calls)
  4. Check current default user registration role
    Go to WordPress admin > Digits Settings > General (or similar) and examine the 'Default User Role' setting, or query the wp_options table for option_name 'digit_default_user_role'
    Affected if The default role is set to an elevated role such as Administrator, Editor, or Author (rather than the default Subscriber)
  5. Audit recent role setting changes
    Review WordPress activity logs, server access logs, or database logs for recent modifications to the digit_default_user_role option, or compare current setting against known-good baseline
    Affected if The default user role was changed without administrator awareness or documentation

A user is affected if the Digits plugin version is 8.4.2 or lower AND the vulnerable settings function exists AND the default user registration role has been modified to an elevated privilege level.

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
Upgrade available Upgrade to a release after 8.4.2
Interim mitigation

Upgrade the Digits plugin to version 8.4.2 or later which includes proper nonce validation. As an interim measure, advise administrators not to click untrusted links, but this does not adequately mitigate the vulnerability.

Recommended fix High confidence

Digits plugin version 8.4.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Digits' plugin in the plugin list
  4. 4. Check if an update is available for the Digits plugin
  5. 5. If an update is available, click 'Update Now' to upgrade to the fixed version
  6. 6. Alternatively, navigate to Dashboard > Updates and update all plugins including Digits
  7. 7. After updating, verify the 'digits_save_settings' function now includes proper nonce validation by reviewing plugin changelog or contacting vendor
Caveat Minor release - review plugin changelog for any compatibility notes with your WordPress version

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

Fix this in Digits Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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