# CVE-2026-12097: User Management <= 1.2 - Missing Authorization to Unauthenticated Plugin Settings Modification

> Unauthenticated attackers can modify plugin settings to control user field exports, potentially exposing sensitive data like password hashes.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-fm3p-77j7-xv3w

## What is CVE-2026-12097?

CVE-2026-12097 is a medium-severity missing authorization vulnerability in saadiqbal User Management, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-12097?


## How do I fix CVE-2026-12097?

No fix has been published for CVE-2026-12097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12097 being exploited?

There is no known exploitation of CVE-2026-12097 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12097 and fix it if it is affected.

What it is: CVE-2026-12097 is a medium-severity missing authorization vulnerability in saadiqbal User Management, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12097 in the wild and no public exploit code.

Affected product: saadiqbal User Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12097/ (Markdown: https://insights.sbomify.com/CVE-2026-12097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12097
- OSV: https://osv.dev/vulnerability/CVE-2026-12097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12097/
Summaries are generated and may contain mistakes; the official description above is the record.