# CVE-2025-25103: WordPress Indeed API Plugin <= 0.5 - CSRF to Settings Change vulnerability

> Attackers can trick authenticated users into changing plugin settings via CSRF, requiring an upgrade to the Indeed API plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 7 Feb 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-x3mv-fv93-fwcg

## What is CVE-2025-25103?

CVE-2025-25103 is a medium-severity vulnerability in bnielsen Indeed API, published on 7 Feb 2025. 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

Cross-Site Request Forgery (CSRF) vulnerability in bnielsen Indeed API indeed-api allows Cross Site Request Forgery.This issue affects Indeed API: from n/a through <= 0.5.

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

## Which versions are affected by CVE-2025-25103?


## How do I fix CVE-2025-25103?

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

## Is CVE-2025-25103 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25103 and fix it if it is affected.

What it is: CVE-2025-25103 is a medium-severity vulnerability in bnielsen Indeed API, published on 7 Feb 2025. 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-2025-25103 in the wild and no public exploit code.

Affected product: bnielsen Indeed API. 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-2025-25103/ (Markdown: https://insights.sbomify.com/CVE-2025-25103/index.md)
```

## Sources

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

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