# CVE-2023-53895: PimpMyLog 1.7.14 Improper Access Control via Account Creation Endpoint

> Remote attackers can create unauthorized admin accounts and inject JavaScript to access sensitive logs and environment variables in PimpMyLog.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-v3r2-q367-cjqr

## What is CVE-2023-53895?

CVE-2023-53895 is a critical missing authorization vulnerability in PimpMyLog, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PimpMyLog 1.7.14 contains an improper access control vulnerability that allows remote attackers to create admin accounts without authorization through the configuration endpoint. Attackers can exploit the unsanitized username field to inject malicious JavaScript, create a hidden backdoor account, and potentially access sensitive server-side log information and environmental variables.

Weakness: CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Potsky Pimp My Log.

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

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

## Is CVE-2023-53895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53895 is a critical missing authorization vulnerability in PimpMyLog, published on 16 Dec 2025. 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-2023-53895 exists.

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

## Sources

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

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