# CVE-2023-4800: DoLogin Security < 3.7.1 - Subscriber+ IP Address leak

> Low-privileged users can view failed login IP addresses due to missing access controls in the DoLogin Security plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 16 Oct 2023
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-8ch2-m9x4-vgjv

## What is CVE-2023-4800?

CVE-2023-4800 is a medium-severity vulnerability in Unknown DoLogin Security, published on 16 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DoLogin Security WordPress plugin before 3.7.1 does not restrict the access of a widget that shows the IPs of failed logins to low privileged users.

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

It affects 1 product.


Products: Wpdo Dologin Security.

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

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

## Is CVE-2023-4800 being exploited?

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

Public exploit code:

- Repository for CVE-2023-4800 vulnerability.  (github_poc): https://github.com/b0marek/CVE-2023-4800

## Other vulnerabilities in Unknown DoLogin Security

- [CVE-2023-4549](https://insights.sbomify.com/CVE-2023-4549/): DoLogin Security < 3.7 - Unauthenticated Stored Cross-Site Scripting (medium 6.1)
- [CVE-2023-4631](https://insights.sbomify.com/CVE-2023-4631/): DoLogin Security < 3.7 - IP Spoofing (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4800 is a medium-severity vulnerability in Unknown DoLogin Security, published on 16 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4800 exists.

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

## Sources

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

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