# CVE-2014-7957: Cross-site request forgery in n/a

> CSRF vulnerabilities in the Pods WordPress plugin allow attackers to hijack administrator sessions to modify settings, delete data, or escalate privileges.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6gr9-w5xf-xjq3

## What is CVE-2014-7957?

CVE-2014-7957 is a medium-severity vulnerability in n/a, published on 15 Jan 2015. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in the Pods plugin before 2.5 for WordPress allow remote attackers to hijack the authentication of administrators for requests that (1) conduct cross-site scripting (XSS) attacks via the toggled parameter in a toggle action in the pods-components page to wp-admin/admin.php, (2) delete a pod in a delete action in the pods page to wp-admin/admin.php, (3) reset pod settings and data via the pods_reset parameter in the pod-settings page to wp-admin/admin.php, (4) deactivate and reset pod data via the pods_reset_deactivate parameter in the pod-settings page to wp-admin/admin.php, (5) delete the admin role via the id parameter in a delete action in the pods-component-roles-and-capabilities page to wp-admin/admin.php, or (6) enable "roles and capabilities" in a toggle action in the pods-components page to wp-admin/admin.php.

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

## Which versions are affected by CVE-2014-7957?

It affects 1 product.


Products: Pods Foundation Pods.

## How do I fix CVE-2014-7957?

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

## Is CVE-2014-7957 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7957 and fix it if it is affected.

What it is: CVE-2014-7957 is a medium-severity vulnerability in n/a, published on 15 Jan 2015. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-7957 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-2014-7957/ (Markdown: https://insights.sbomify.com/CVE-2014-7957/index.md)
```

## Sources

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

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