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

> Cross-site request forgery in the Accurate Form Data Real Time Form Validation plugin allows attackers to inject malicious scripts via admin settings.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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:** 26 Sep 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3f8v-r6fv-2xv4

## What is CVE-2015-9443?

CVE-2015-9443 is a medium-severity vulnerability in n/a, published on 26 Sep 2019. 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 accurate-form-data-real-time-form-validation plugin 1.2 for WordPress has CSRF with resultant XSS via wp-admin/options-general.php?page=Accu_Data_WP.

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

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

It affects 1 product.


Products: Wp Accurate Form Data Project Wp Accurate Form Data.

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

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

## Is CVE-2015-9443 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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