# CVE-2017-6213: paypal/invoice-sdk-php reflected XSS

> Reflected XSS in the PayPal Invoice SDK PHP library allows attackers to execute arbitrary code via the permToken parameter.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-626w-hmpw-x74j

## What is CVE-2017-6213?

CVE-2017-6213 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Aug 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

paypal/invoice-sdk-php is vulnerable to reflected XSS in samples/permissions.php via the permToken parameter, resulting in code execution.

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

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

2 open source packages ship an affected version, including paypal/invoice-sdk-php. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `paypal/invoice-sdk-php` | Packagist | All versions to 3.9.0 | None |
| `paypal/invoice-sdk-php` | Packagist | All versions to 3.9.0 | None |

Products: Paypal Php Invoice Sdk.

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

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

## Is CVE-2017-6213 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6213 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Aug 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6213 in the wild and no public exploit code.

Affected packages and fixed versions:
- paypal/invoice-sdk-php (Packagist): affected all versions up to 3.9.0; no fix listed
- paypal/invoice-sdk-php (Packagist): affected all versions up to 3.9.0; no fix listed

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

## Sources

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

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