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

> Remote attackers can inject arbitrary web script or HTML via user profile fields in Webfolio CMS, potentially leading to session hijacking or malicious actions.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-44wq-5x49-35cx

## What is CVE-2012-1899?

CVE-2012-1899 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Sep 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in webfolio/admin/users/edit in Webfolio CMS 1.1.4 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) First name, (2) Last name or (3) Email (required) fields.

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

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

It affects 1 product.


Products: Nikola Posa Webfoliocms.

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

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

## Is CVE-2012-1899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1899 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Sep 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-1899 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-1899/ (Markdown: https://insights.sbomify.com/CVE-2012-1899/index.md)
```

## Sources

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

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