# CVE-2026-16262: Estatik < 4.3.3 - Login CSRF

> An attacker can force a victim to log into an attacker-controlled account via OAuth, allowing the attacker to read the victim's subsequent activity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-jqr2-6x6h-fvmp

## What is CVE-2026-16262?

CVE-2026-16262 is a high-severity vulnerability in Unknown Estatik Real Estate Plugin, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Estatik Real Estate Plugin WordPress plugin before 4.3.3 does not bind its OAuth social login flow to the initiating user session, allowing an unauthenticated attacker to log a victim into an attacker-controlled account (login CSRF), so that the victim's subsequent activity is stored under and readable by the attacker.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-16262 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16262 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16262 is a high-severity vulnerability in Unknown Estatik Real Estate Plugin, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16262 exists.

Affected product: Unknown Estatik Real Estate Plugin. 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-16262/ (Markdown: https://insights.sbomify.com/CVE-2026-16262/index.md)
```

## Sources

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

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