# CVE-2015-9233: Cross-site request forgery in n/a

> Cross-site request forgery in the CP Contact Form with PayPal plugin allows attackers to inject malicious scripts, leading to potential code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 29 Sep 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mp67-fwx4-7wm9

## What is CVE-2015-9233?

CVE-2015-9233 is a high-severity vulnerability in n/a, published on 29 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

The cp-contact-form-with-paypal (aka CP Contact Form with PayPal) plugin before 1.1.6 for WordPress has CSRF with resultant XSS, related to cp_contactformpp.php and cp_contactformpp_admin_int_list.inc.php.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2015-9233?

It affects 1 product.


Products: Codepeople Cp Contact Form With Paypal.

## How do I fix CVE-2015-9233?

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

## Is CVE-2015-9233 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14784](https://insights.sbomify.com/CVE-2019-14784/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-14785](https://insights.sbomify.com/CVE-2019-14785/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2023-27460](https://insights.sbomify.com/CVE-2023-27460/): Missing authorization in CP Contact Form with Paypal (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-9233 and fix it if it is affected.

What it is: CVE-2015-9233 is a high-severity vulnerability in n/a, published on 29 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-2015-9233 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-2015-9233/ (Markdown: https://insights.sbomify.com/CVE-2015-9233/index.md)
```

## Sources

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

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