CVE-2026-13741
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 Digits: WordPress Mobile Number Signup and Login plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 9.1.0.5. This is due to missing authorization and role validation in the `dig_update_wpwc_custom_fields()` function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate their privileges to Administrator by submitting a forged `digits_reg_userrole` value during profile update, granted the site administrator has configured the built-in DIGITS User Role field.
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 Digits WordPress plugin up to version 9.1.0.5 contains a privilege escalation vulnerability in the `dig_update_wpwc_custom_fields()` function due to missing authorization checks and role validation. Authenticated users with Subscriber-level access or higher can submit a forged `digits_reg_userrole` parameter during profile updates to escalate their privileges to Administrator, provided the site administrator has configured the built-in DIGITS User Role field.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Digits plugin installationCheck your WordPress plugins directory or the WordPress admin Plugins page for the Digits plugin. Note the installed version number.Affected if The Digits plugin is not installed on the WordPress site.
-
Compare installed version to affected rangeCompare the installed Digits plugin version against version 9.1.0.6. Check the plugin header in the main plugin file (typically digits.php or similar in wp-content/plugins/digits) for the Version field.Affected if The installed version is lower than 9.1.0.6.
-
Locate the DIGITS User Role field configurationIn the WordPress admin dashboard, navigate to Digits plugin settings. Look for a field labeled DIGITS User Role, User Role, or similar role assignment configuration. This is typically found under Digits Settings > General or a similar settings section.Affected if The DIGITS User Role field is present and has been configured (has a selected value) by an administrator.
-
Verify subscriber-level access existsCheck if there are any users with the Subscriber role on the site, or if the site allows user registration that results in Subscriber-level accounts.Affected if Subscriber-level user accounts exist or can be created on the site.
A site is affected if the Digits plugin version is below 9.1.0.6, the DIGITS User Role field is configured in plugin settings, and subscriber-level user accounts are present or can be created.
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 Digits plugin to a version beyond 9.1.0.5 when available. Until then, disable the DIGITS User Role field configuration and review user accounts for unauthorized administrator privileges.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13741 — 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-2026-13741 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