# CVE-2013-6923: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script via admin parameters, potentially leading to code execution or account takeover on Seagate BlackArmor NAS devices.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/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:** 9 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-22m9-22wm-6qxh

## What is CVE-2013-6923?

CVE-2013-6923 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jan 2014. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Seagate BlackArmor NAS 220 devices with firmware sg2000-2000.1331 allow remote attackers to inject arbitrary web script or HTML via the (1) fullname parameter to admin/access_control_user_edit.php or (2) workname parameter to admin/network_workgroup_domain.php.

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

## Which versions are affected by CVE-2013-6923?

It affects 2 products.


Products: Seagate Blackarmor Nas 220, Seagate Blackarmor Nas 220 Firmware.

## How do I fix CVE-2013-6923?

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

## Is CVE-2013-6923 being exploited?

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

Public exploit code:

- Seagate BlackArmor NAS sg2000-2000.1331 - Multiple Persistent Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-6922](https://insights.sbomify.com/CVE-2013-6922/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6923 and fix it if it is affected.

What it is: CVE-2013-6923 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jan 2014. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6923 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-2013-6923/ (Markdown: https://insights.sbomify.com/CVE-2013-6923/index.md)
```

## Sources

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

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