# CVE-2026-82519: Really Simple Security < 9.8.2 Authorization Bypass via profile-page update handler

> Authenticated low-privileged users can bypass mandatory two-factor authentication enforcement by exploiting a missing authorization check in the profile update handler.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 20 Sep 2026
- **Also known as:** GHSA-794h-mjxc-xmmh

## What is CVE-2026-82519?

CVE-2026-82519 is a low-severity missing authorization vulnerability in reallysimpleplugins Really Simple Security, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Really Simple Security plugin for WordPress before 9.8.2 contains a missing authorization check vulnerability that allows authenticated low-privileged attackers to bypass enforced two-factor authentication indefinitely by exploiting an unguarded code path in the profile-page update handler. Attackers can submit a crafted POST request without the two-factor-authentication field to skip nonce verification and trigger delete_two_fa_meta(), which resets the grace period anchor timestamp on every login cycle, causing mandatory 2FA enforcement to be deferred indefinitely.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-82519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82519 is a low-severity missing authorization vulnerability in reallysimpleplugins Really Simple Security, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82519 in the wild and no public exploit code.

Affected product: reallysimpleplugins Really Simple Security. 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-82519/ (Markdown: https://insights.sbomify.com/CVE-2026-82519/index.md)
```

## Sources

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

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