# CVE-2010-4275: Cross-site scripting in n/a

> Remote authenticated administrators can inject arbitrary web script or HTML via specific parameters in Radius Manager, potentially leading to session hijacking or malicious actions.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f8mw-q536-545m

## What is CVE-2010-4275?

CVE-2010-4275 is a low-severity cross-site scripting vulnerability in n/a, published on 22 Dec 2010. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Radius Manager 3.8.0 allow remote authenticated administrators to inject arbitrary web script or HTML via the (1) name or (2) descr parameter in an (a) update_usergroup or a (b) store_nas action to admin.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2010-4275?

It affects 1 product.


Products: Dmasoftlab Radius Manager.

## How do I fix CVE-2010-4275?

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

## Is CVE-2010-4275 being exploited?

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

Public exploit code:

- Radius Manager 3.8.0 - Multiple Cross-Site Scripting Vulnerabilities (exploitdb)
- Radius Manager 3.6 - Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-30147](https://insights.sbomify.com/CVE-2021-30147/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4275 and fix it if it is affected.

What it is: CVE-2010-4275 is a low-severity cross-site scripting vulnerability in n/a, published on 22 Dec 2010. 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-2010-4275 exists.

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

## Sources

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

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