# CVE-2026-18052: ManageWP Worker < 4.9.37 - Unauthenticated Authentication Bypass via Unsigned Auto-Login Parameters

> Attackers can gain administrator sessions by replaying unsigned auto-login links, bypassing authentication in the ManageWP Worker plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** GHSA-3mmr-x4g9-xv4w

## What is CVE-2026-18052?

CVE-2026-18052 is a high-severity authentication bypass vulnerability in Unknown ManageWP Worker, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ManageWP Worker WordPress plugin before 4.9.37 does not bind the account being logged in to the signature which authorises the login, nor prevent an already used login link from being replayed, allowing attackers who obtain such a link to gain a session as any user on the site, including an administrator.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-18052 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18052 is a high-severity authentication bypass vulnerability in Unknown ManageWP Worker, published on 22 Aug 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-18052 in the wild and no public exploit code.

Affected product: Unknown ManageWP Worker. 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-18052/ (Markdown: https://insights.sbomify.com/CVE-2026-18052/index.md)
```

## Sources

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

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