# CVE-2012-1829: Cross-site scripting in n/a

> Remote authenticated users can inject arbitrary web script or HTML into AutoFORM PDM Archive via unspecified fields.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2xm8-8vq5-f8xg

## What is CVE-2012-1829?

CVE-2012-1829 is a low-severity cross-site scripting vulnerability in n/a, published on 13 Jun 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in AutoFORM PDM Archive before 6.920 allow remote authenticated users to inject arbitrary web script or HTML via unspecified fields.

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

## Which versions are affected by CVE-2012-1829?

It affects 1 product.


Products: Efstechnology Autoform Pdm Archive.

## How do I fix CVE-2012-1829?

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

## Is CVE-2012-1829 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1827](https://insights.sbomify.com/CVE-2012-1827/): Missing authorization in n/a (medium 6.5)
- [CVE-2012-1828](https://insights.sbomify.com/CVE-2012-1828/): Missing authorization in n/a (medium 6.5)
- [CVE-2012-3347](https://insights.sbomify.com/CVE-2012-3347/): Auth bypass in n/a (medium 6.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1829 and fix it if it is affected.

What it is: CVE-2012-1829 is a low-severity cross-site scripting vulnerability in n/a, published on 13 Jun 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-1829 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-2012-1829/ (Markdown: https://insights.sbomify.com/CVE-2012-1829/index.md)
```

## Sources

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

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