# CVE-2022-44244: Lin CMS vulnerable to Improper Authentication

> Attackers can bypass authentication to escalate privileges to Super Administrator in Lin-CMS.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/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:** 9 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-4vrc-q7m6-vq7w, PYSEC-2026-839

## What is CVE-2022-44244?

CVE-2022-44244 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authentication bypass in Lin-CMS v0.2.1 allows attackers to escalate privileges to Super Administrator.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-44244?

5 open source packages ship an affected version, including io.github.talelin:lin-cms-core, Lin-CMS and lin-cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.github.talelin:lin-cms-core` | Maven | All versions to 0.2.1 | None |
| `io.github.talelin:lin-cms-core` | Maven | All versions to 0.2.1 | None |
| `Lin-CMS` | PyPI | All versions to 0.2.1 | None |
| `lin-cms` | PyPI | All versions to 0.2.1 | None |
| `lin-cms` | PyPI | All versions to 0.2.1 | None |

Products: Lin-Cms Project Lin-Cms.

## How do I fix CVE-2022-44244?

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

## Is CVE-2022-44244 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44244 and fix it if it is affected.

What it is: CVE-2022-44244 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Nov 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44244 exists.

Affected packages and fixed versions:
- io.github.talelin:lin-cms-core (Maven): affected all versions up to 0.2.1; no fix listed
- io.github.talelin:lin-cms-core (Maven): affected all versions up to 0.2.1; no fix listed
- Lin-CMS (PyPI): affected all versions up to 0.2.1; no fix listed
- lin-cms (PyPI): affected all versions up to 0.2.1; no fix listed
- lin-cms (PyPI): affected all versions up to 0.2.1; no fix listed

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-2022-44244/ (Markdown: https://insights.sbomify.com/CVE-2022-44244/index.md)
```

## Sources

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

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