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

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in Apache OFBiz, potentially leading to session hijacking or data theft.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 15 Apr 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hr4m-h57x-5p2p

## What is CVE-2010-0432?

CVE-2010-0432 is a medium-severity cross-site scripting vulnerability in Apache Ofbiz, published on 15 Apr 2010. 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

Multiple cross-site scripting (XSS) vulnerabilities in the Apache Open For Business Project (aka OFBiz) 09.04 and earlier, as used in Opentaps, Neogia, and Entente Oya, allow remote attackers to inject arbitrary web script or HTML via (1) the productStoreId parameter to control/exportProductListing, (2) the partyId parameter to partymgr/control/viewprofile (aka partymgr/control/login), (3) the start parameter to myportal/control/showPortalPage, (4) an invalid URI beginning with /facility/control/ReceiveReturn (aka /crmsfa/control/ReceiveReturn or /cms/control/ReceiveReturn), (5) the contentId parameter (aka the entityName variable) to ecommerce/control/ViewBlogArticle, (6) the entityName parameter to webtools/control/FindGeneric, or the (7) subject or (8) content parameter to an unspecified component under ecommerce/control/contactus.

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

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

It affects 1 product.


Products: Apache Ofbiz.

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

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

## Is CVE-2010-0432 being exploited?

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

Public exploit code:

- Apache OFBiz - Remote Execution (via SQL Execution) (exploitdb)
- Apache OFBiz - Admin Creator (exploitdb)
- Apache OFBiz - Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in Apache Ofbiz

- [CVE-2024-45195](https://insights.sbomify.com/CVE-2024-45195/): Apache OFBiz Forced Browsing (critical 9.8, exploited in the wild)
- [CVE-2024-32113](https://insights.sbomify.com/CVE-2024-32113/): Apache OFBiz Path Traversal (critical 9.1, exploited in the wild)
- [CVE-2024-38856](https://insights.sbomify.com/CVE-2024-38856/): Apache OFBiz Incorrect Authorization (high 8.1, exploited in the wild)
- [CVE-2013-2250](https://insights.sbomify.com/CVE-2013-2250/): Code injection in n/a (critical 10.0)
- [CVE-2012-3506](https://insights.sbomify.com/CVE-2012-3506/): Unspecified vulnerability in the Apache Open For Business Project (aka OFBiz) 10.04.x before 10.04.03 has unknown impact and attack vectors. (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0432 is a medium-severity cross-site scripting vulnerability in Apache Ofbiz, published on 15 Apr 2010. 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-2010-0432 exists.

Affected product: Apache Ofbiz. 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-0432/ (Markdown: https://insights.sbomify.com/CVE-2010-0432/index.md)
```

## Sources

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

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