# CVE-2026-105290: feelec-yishu feelcrm-os getCurlData Endpoint GoogleController.class.php server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the getCurlData endpoint of feelcrm-os to access internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-j6f9-frhx-wfq4

## What is CVE-2026-105290?

CVE-2026-105290 is a medium-severity server-side request forgery vulnerability in feelec-yishu feelcrm-os, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in feelec-yishu feelcrm-os 1.0.0. This affects an unknown part of the file App/Feelcrm/Index/Controller/GoogleController.class.php of the component getCurlData Endpoint. Executing a manipulation of the argument url can lead to server-side request forgery. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-105290?


## How do I fix CVE-2026-105290?

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

## Is CVE-2026-105290 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105290 and fix it if it is affected.

What it is: CVE-2026-105290 is a medium-severity server-side request forgery vulnerability in feelec-yishu feelcrm-os, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105290 exists.

Affected product: feelec-yishu feelcrm-os. 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-2026-105290/ (Markdown: https://insights.sbomify.com/CVE-2026-105290/index.md)
```

## Sources

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

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