# CVE-2017-1002017: Cross-site scripting in gift-certificate-creator

> A stored XSS vulnerability in the gift-certificate-creator WordPress plugin allows attackers to inject malicious scripts via unsanitized user input.

- **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:** 14 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5x4j-f676-6cj8

## What is CVE-2017-1002017?

CVE-2017-1002017 is a medium-severity cross-site scripting vulnerability in Bob Cares gift-certificate-creator, published on 14 Sep 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

Vulnerability in wordpress plugin gift-certificate-creator v1.0, The code in gc-list.php doesn't sanitize user input to prevent a stored XSS vulnerability.

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

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

It affects 1 product.


Products: Bobcares Gift-Certificate-Creator.

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

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

## Is CVE-2017-1002017 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1002017 is a medium-severity cross-site scripting vulnerability in Bob Cares gift-certificate-creator, published on 14 Sep 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: There is no known exploitation of CVE-2017-1002017 in the wild and no public exploit code.

Affected product: Bob Cares gift-certificate-creator. 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-1002017/ (Markdown: https://insights.sbomify.com/CVE-2017-1002017/index.md)
```

## Sources

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

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