PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-105290 feelec-yishu CVE debrief

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.

Vendor
feelec-yishu
Product
feelcrm-os
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-05
Original CVE updated
2026-10-05
Advisory published
2026-10-05
Advisory updated
2026-10-05

Who should care

Defenders responsible for feelec-yishu feelcrm-os 1.0.0 deployments should assess exposure and potential for server-side request forgery attacks. They should verify the getCurlData endpoint exposure and evaluate potential impacts on affected systems. Defenders should also prioritize verifying exposure and assessing potential impacts due to public disclosure of the exploit.

Why it matters

Defenders should prioritize verifying exposure of the getCurlData endpoint in feelec-yishu feelcrm-os 1.0.0 and assessing the potential for server-side request forgery attacks due to public disclosure of the exploit.

  • Potential for server-side request forgery attacks
  • Public disclosure of exploit may increase attack attempts
  • Limited information on actual exploitation or impact

Technical summary

The vulnerability affects the getCurlData endpoint in feelec-yishu feelcrm-os 1.0.0, allowing for server-side request forgery attacks. The exploit has been publicly disclosed. The project was informed of the problem early through an issue report but has not responded yet. Affected product deployments should be verified for exposure and potential impact assessed by defenders responsible for these systems. The vulnerability allows for server-side request forgery attacks due to manipulation of the url argument in the getCurlData endpoint.

Defensive priority

Defenders should prioritize verifying exposure of the getCurlData endpoint in feelec-yishu feelcrm-os 1.0.0 and assessing the potential for server-side request forgery attacks.

Recommended defensive actions

  • Verify exposure of the getCurlData endpoint in feelec-yishu feelcrm-os 1.0.0
  • Assess the potential for server-side request forgery attacks
  • Monitor for publicly disclosed exploits
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions, retest remediated assets
  • Plan vendor-supported updates or mitigations through normal change control

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. The exploit has been publicly disclosed, but there is no information on actual exploitation or impact. Defenders should verify the getCurlData endpoint in feelec-yishu feelcrm-os 1.0.0 for exposure and assess potential server-side request forgery attacks. Evidence is limited to CVE and NVD entries.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-105290 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-105290

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-105290 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105290

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.