dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12097

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 User Management plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify the plugin's export field configuration stored in the uiewp_export_field option, controlling which user fields such as password hashes are included in CSV exports and how columns are mapped during imports.

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 User Management WordPress plugin has an authorization bypass vulnerability in versions up to 1.2. Unauthenticated attackers can modify the uiewp_export_field option to control which user fields (including password hashes) are exported in CSV format. This allows unauthorized exfiltration of sensitive user data through the plugin's export functionality.

MitigationUpdate to a patched version of the plugin when available; until then, consider disabling the plugin or adding firewall rules to block unauthorized access to the affected endpoints. Also audit recent user exports and consider password resets as a precaution.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 User Management plugin is installed
    Go to WordPress admin > Plugins and look for 'User Management' plugin in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check for 'user-management' or similar plugin slug.
    Affected if The plugin appears in the active plugins list
  2. Identify the installed plugin version
    Check the plugin header in wp-content/plugins/user-management/user-management.php for the 'Version' comment, or query the database: SELECT option_value FROM wp_options WHERE option_name LIKE '%user_management%version%'.
    Affected if The version is 1.2 or lower, or no version is displayed (which typically means an unpatched older release)
  3. Verify the uiewp_export_field option exists
    Query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'uiewp_export_field'. If the option exists and contains user field names, the vulnerable configuration is present.
    Affected if The option exists and is populated with field names, indicating the export functionality is configured
  4. Test if the export endpoint accepts unauthenticated requests
    Send a GET or POST request to the plugin export URL (commonly /wp-admin/admin-ajax.php?action=uiewp_user_export or similar endpoint) without providing authentication cookies or credentials, using curl or a browser.
    Affected if The request returns CSV data or processes without returning a 401/403 authentication error
  5. Check if password hashes appear in exportable fields
    Review the value of the uiewp_export_field option: if it includes 'user_pass', 'pwd', or similar field names, password hashes could be exported. Query: SELECT option_value FROM wp_options WHERE option_name = 'uiewp_export_field'.
    Affected if The option value contains 'user_pass' or indicates password fields are included in the export configuration

A user is affected if the User Management plugin versions 1.2 or below is installed and active, the uiewp_export_field option exists in the database, and the export functionality is accessible without authentication.

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

Update to a patched version of the plugin when available; until then, consider disabling the plugin or adding firewall rules to block unauthorized access to the affected endpoints. Also audit recent user exports and consider password resets as a precaution.

Recommended fix Moderate confidence

Latest version of User Management plugin (version higher than 1.2)

  1. Check the current installed version of the User Management plugin in WordPress admin under Plugins > Installed Plugins
  2. If the installed version is 1.2 or lower, navigate to Plugins > Add New > Upload Plugin or check the plugin repository for an updated version
  3. Upload and install the latest version of the User Management plugin that addresses CVE-2026-12097
  4. After updating, verify the plugin settings under the plugin's admin menu to ensure configuration is intact
  5. Review the uiewp_export_field option in the database (via wp_options table or plugin settings) to confirm it has not been tampered with by attackers
  6. If unauthorized changes are detected, reset the export field configuration to safe defaults (exclude sensitive fields like password hashes from exports)
  7. Test that CSV export and import functionality works correctly with the updated version
  8. Consider implementing additional access controls or WordPress security plugins to monitor for unauthorized option changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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