# CVE-2022-23475: dalorRadius full account take over

> Attackers can hijack user accounts via XSS and CSRF vulnerabilities in the daloRADIUS web management interface.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 6 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-c9xx-6mvw-9v84

## What is CVE-2022-23475?

CVE-2022-23475 is a high-severity cross-site scripting vulnerability in lirantal daloradius, published on 6 Dec 2022. 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

daloRADIUS is an open source RADIUS web management application. daloRadius 1.3 and prior are vulnerable to a combination cross site scripting (XSS) and cross site request forgery (CSRF) vulnerability which leads to account takeover in the mng-del.php file because of an unescaped variable reflected in the DOM on line 116. This issue has been addressed in commit `ec3b4a419e`. Users are advised to manually apply the commit in order to mitigate this issue. Users may also mitigate this issue with in two parts 1) The CSRF vulnerability can be mitigated  by making the daloRadius session cookie to samesite=Lax or by the implimentation of a CSRF token in all forms. 2) The XSS vulnerability may be mitigated by escaping it or by introducing a Content-Security policy.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Daloradius Daloradius.

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

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

## Is CVE-2022-23475 being exploited?

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

## Other vulnerabilities in lirantal daloradius

- [CVE-2023-0046](https://insights.sbomify.com/CVE-2023-0046/): Improper Restriction of Names for Files and Other Resources in lirantal/daloradius (high 7.2)
- [CVE-2023-0048](https://insights.sbomify.com/CVE-2023-0048/): Code Injection in lirantal/daloradius (high 7.2)
- [CVE-2023-0337](https://insights.sbomify.com/CVE-2023-0337/): Cross-site Scripting (XSS) - Reflected in lirantal/daloradius (medium 5.8)
- [CVE-2023-0338](https://insights.sbomify.com/CVE-2023-0338/): Cross-site Scripting (XSS) - Reflected in lirantal/daloradius (medium 5.8)
- [CVE-2022-4630](https://insights.sbomify.com/CVE-2022-4630/): Sensitive Cookie Without 'HttpOnly' Flag in lirantal/daloradius (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23475 is a high-severity cross-site scripting vulnerability in lirantal daloradius, published on 6 Dec 2022. 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-2022-23475 exists.

Affected product: lirantal daloradius. 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-2022-23475/ (Markdown: https://insights.sbomify.com/CVE-2022-23475/index.md)
```

## Sources

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

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