# CVE-2023-23192: Auth bypass in n/a

> Attackers can bypass authentication in IS Decisions UserLock MFA by exploiting a scheduled task vulnerability.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-cgm5-694g-9m5c

## What is CVE-2023-23192?

CVE-2023-23192 is a high-severity authentication bypass vulnerability in n/a, published on 23 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IS Decisions UserLock MFA 11.01 is vulnerable to authentication bypass using scheduled task.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Isdecisions Userlock.

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

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

## Is CVE-2023-23192 being exploited?

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

Public exploit code:

- CVE-2023-23192 (github_poc): https://github.com/pinarsadioglu/CVE-2023-23192

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23192 is a high-severity authentication bypass vulnerability in n/a, published on 23 Mar 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-23192 in the wild and no public exploit code.

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

## Sources

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

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