# CVE-2017-17043: Cross-site scripting in n/a

> Reflected XSS in Emag Marketplace Connector allows attackers to inject scripts via the post parameter, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 28 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-936x-ffmv-qh66

## What is CVE-2017-17043?

CVE-2017-17043 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Nov 2017. 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

The Emag Marketplace Connector plugin 1.0.0 for WordPress has reflected XSS because the parameter "post" to /wp-content/plugins/emag-marketplace-connector/templates/order/awb-meta-box.php is not filtered correctly.

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

## Which versions are affected by CVE-2017-17043?

It affects 1 product.


Products: Zitec Emag Marketplace Connector.

## How do I fix CVE-2017-17043?

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

## Is CVE-2017-17043 being exploited?

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

Public exploit code:

- WordPress Emag Marketplace Connector 1.0 - Cross-Site Scripting (nuclei): http/cves/2017/CVE-2017-17043.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17043 and fix it if it is affected.

What it is: CVE-2017-17043 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Nov 2017. 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-2017-17043 exists.

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-2017-17043/ (Markdown: https://insights.sbomify.com/CVE-2017-17043/index.md)
```

## Sources

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

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