dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-0912

HIGH · 8.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Toret Manager plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'trman_save_option' function and on the 'trman_save_option_items' in all versions up to, and including, 1.2.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 Toret Manager WordPress plugin versions up to 1.2.7 lack capability checks on the 'trman_save_option' and 'trman_save_option_items' functions, allowing any authenticated user with Subscriber-level access or higher to modify arbitrary WordPress options. Attackers can exploit this to change the default user registration role to Administrator and enable user registration, creating an admin account for full site compromise.

MitigationUpgrade to version 1.2.8 or later which includes proper capability validation. If immediate upgrade is not possible, disable the plugin or restrict user registration until the patch can be applied.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Toret Manager plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, find 'Toret Manager' and note the version number displayed. Alternatively, inspect the main plugin file (typically /wp-content/plugins/toret-manager/ or similar naming) and read the version in the plugin header comment.
    Affected if The installed version is 1.2.7 or lower.
  2. Verify user registration is enabled
    Go to WordPress admin > Settings > General > 'Membership' section and check if 'Anyone can register' is checked. Note the default role setting.
    Affected if User registration is enabled, especially with Administrator set as the default role.
  3. Audit administrator accounts
    Navigate to WordPress admin > Users and review all accounts with Administrator role. Check creation dates and email addresses for anything suspicious or unfamiliar.
    Affected if There are administrator accounts you did not create, or accounts created recently that you cannot explain.
  4. Inspect plugin AJAX endpoints
    Check the plugin directory for AJAX action handlers referencing 'trman_save_option' or 'trman_save_option_items'. In a default install, look in the main plugin PHP file for do_action('wp_ajax_trman_save_option') or similar hooks.
    Affected if These functions exist without capability checks (look for 'manage_options' or 'edit_users' capability verification before the action runs).

You are affected if Toret Manager plugin version 1.2.7 or lower is installed AND your site has user registration enabled, resulting in unauthorized admin accounts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.2.8 or later which includes proper capability validation. If immediate upgrade is not possible, disable the plugin or restrict user registration until the patch can be applied.

Recommended fix Moderate confidence

Latest version in WordPress plugin repository (version 1.2.8 or later)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Toret Manager plugin and check for available updates
  4. Update Toret Manager to the latest version available in the WordPress plugin repository (version 1.2.8 or later)
  5. After updating, verify no unauthorized administrator accounts were created by reviewing Users > All Users
  6. Consider changing passwords for existing administrator accounts as a precautionary measure

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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