# CVE-2023-4307: Lock User Account <= 1.0.3 - Arbitrary Account Lock/Unlock via CSRF

> Attackers can force admins to lock or unlock arbitrary user accounts via CSRF, potentially disrupting access or bypassing security controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Sep 2023
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-pj3h-qmr5-3qpv

## What is CVE-2023-4307?

CVE-2023-4307 is a medium-severity vulnerability in Unknown Lock User Account, published on 11 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Lock User Account WordPress plugin through 1.0.3 does not have CSRF check when bulk locking and unlocking accounts, which could allow attackers to make logged in admins lock and unlock arbitrary users via a CSRF attack

## Which versions are affected by CVE-2023-4307?

It affects 1 product.


Products: Teknigar Lock User Account.

## How do I fix CVE-2023-4307?

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

## Is CVE-2023-4307 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4307 and fix it if it is affected.

What it is: CVE-2023-4307 is a medium-severity vulnerability in Unknown Lock User Account, published on 11 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4307 exists.

Affected product: Unknown Lock User Account. 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-2023-4307/ (Markdown: https://insights.sbomify.com/CVE-2023-4307/index.md)
```

## Sources

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

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