# CVE-2014-4312: Multiple cross-site scripting (XSS) vulnerabilities in Epicor Enterprise 7.4 before FS74SP6_HotfixTL054181 allow remote attackers to inject


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rvhg-jhq4-7wh7

## What is CVE-2014-4312?

CVE-2014-4312 is a medium-severity vulnerability in n/a, published on 10 Oct 2014. 

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in Epicor Enterprise 7.4 before FS74SP6_HotfixTL054181 allow remote attackers to inject arbitrary web script or HTML via the (1) Notes section to Order details; (2) Description section to "Order to consume"; (3) Favorites name section to Favorites; (4) FiltKeyword parameter to Procurement/EKPHTML/search_item_bt.asp; (5) Act parameter to Procurement/EKPHTML/EnterpriseManager/Budget/ImportBudget_fr.asp; (6) hdnOpener or (7) hdnApproverFieldName parameter to Procurement/EKPHTML/EnterpriseManager/UserSearchDlg.asp; or (8) INTEGRATED parameter to Procurement/EKPHTML/EnterpriseManager/Codes.asp.

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

## Which versions are affected by CVE-2014-4312?

It affects 1 product.


Products: Epicor Epicor Enterprise.

## How do I fix CVE-2014-4312?

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

## Is CVE-2014-4312 being exploited?

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

Public exploit code:

- Epicor Enterprise 7.4 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-4311](https://insights.sbomify.com/CVE-2014-4311/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4312 and fix it if it is affected.

What it is: CVE-2014-4312 is a medium-severity vulnerability in n/a, published on 10 Oct 2014. 
Exploitation: There is no known exploitation of CVE-2014-4312 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-2014-4312/ (Markdown: https://insights.sbomify.com/CVE-2014-4312/index.md)
```

## Sources

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

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