Digits: WordPress Mobile Number Signup and Login <= 9.1.0.5 - Authenticated (Subscriber+) Privilege Escalation via 'digits_reg_userrole' Parameter
The 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.
Quick answer
Digits: WordPress Mobile Number Signup and Login should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-9.1.0.5
Fixed versions
- 9.1.0.6
How to fix it
CVE-2026-13741 is a privilege escalation issue in Digits: WordPress Mobile Number Signup and Login. Update from *-9.1.0.5 to 9.1.0.6 or newer. Keep the fix simple: upgrade first, then test the normal user flow.
- Find every place where Digits: WordPress Mobile Number Signup and Login is installed or used.
- Upgrade Digits: WordPress Mobile Number Signup and Login to 9.1.0.6 or a newer fixed release from the vendor.
- If you cannot upgrade right away, limit access to the affected feature until the update is done.
- Restart or redeploy the service if the product needs it after the update.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is 9.1.0.6 or newer.
- Run a normal login, admin, and user flow to make sure the site still works.
- Check logs for new errors after the update.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-13741?
Digits: WordPress Mobile Number Signup and Login versions listed as affected should be reviewed: *-9.1.0.5.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.