# CVE-2025-10635: Find Me On <= 2.0.9.1 - Subscriber+ SQL Injection

> Subscribers can perform SQL injection attacks in the Find Me On WordPress plugin due to unsanitized parameters.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-fr62-25w9-h4qq

## What is CVE-2025-10635?

CVE-2025-10635 is a high-severity SQL injection vulnerability in Unknown Find Me On, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Find Me On WordPress plugin through 2.0.9.1 does not sanitize and escape a parameter before using it in a SQL statement, allowing subscribers and above to perform SQL injection attacks

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


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

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

## Is CVE-2025-10635 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10635 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10635 is a high-severity SQL injection vulnerability in Unknown Find Me On, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10635 exists.

Affected product: Unknown Find Me On. 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-10635/ (Markdown: https://insights.sbomify.com/CVE-2025-10635/index.md)
```

## Sources

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

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