# CVE-2026-9178: WP Forms Connector <= 1.8 - Missing Authorization to Unauthenticated Information Exposure via 'user/list' REST Endpoint

> Unauthenticated attackers can retrieve sensitive user data, including password hashes, due to missing authorization checks in the WP Forms Connector plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-q7pg-wxgw-7v4g

## What is CVE-2026-9178?

CVE-2026-9178 is a high-severity missing authorization vulnerability in hancock11 WP Forms Connector, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Forms Connector plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.8. The plugin registers the REST route wp/v3/user/list/<id> (callback userDetail()) with permission_callback set to '__return_true', and the function's home-grown authentication only verifies that the supplied 'Username' HTTP header maps to an administrator account and that a 'Password' HTTP header is non-empty. It never validates the password with wp_check_password() (unlike the sibling delete_wc_user() function which does). This makes it possible for unauthenticated attackers to retrieve sensitive information for any registered user ID — including the WordPress password hash (user_pass) and email address — by sending a request with a valid administrator login name (commonly the default 'admin') and any arbitrary password value.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-9178 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9178 is a high-severity missing authorization vulnerability in hancock11 WP Forms Connector, published on 24 Jun 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-9178 in the wild and no public exploit code.

Affected product: hancock11 WP Forms Connector. 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-9178/ (Markdown: https://insights.sbomify.com/CVE-2026-9178/index.md)
```

## Sources

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

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