Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105290 Overview
CVE-2026-105290 is a Server-Side Request Forgery (SSRF) vulnerability in feelec-yishu feelcrm-os version 1.0.0. The flaw resides in the getCurlData endpoint implemented in App/Feelcrm/Index/Controller/GoogleController.class.php. An attacker can manipulate the url argument to force the application server to issue arbitrary HTTP requests on their behalf. The attack is remotely exploitable without authentication or user interaction, and the exploit has been publicly disclosed. The upstream project was notified through an issue report but has not yet responded.
Critical Impact
Unauthenticated remote attackers can coerce the server into making arbitrary outbound requests, enabling internal network reconnaissance, access to cloud metadata endpoints, and interaction with services exposed only to the server.
Affected Products
- feelec-yishu feelcrm-os 1.0.0
- Component: App/Feelcrm/Index/Controller/GoogleController.class.php
- Endpoint: getCurlData
Discovery Timeline
- 2026-10-05 - CVE-2026-105290 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-105290
Vulnerability Analysis
The vulnerability is classified as Server-Side Request Forgery under [CWE-918]. The getCurlData function in the GoogleController class accepts a user-controlled url parameter and passes it to a cURL request without validating the destination. Because the server performs the HTTP request, the attacker can reach hosts that are otherwise unreachable from the public internet. These targets include internal services, loopback interfaces, and cloud instance metadata endpoints such as the AWS 169.254.169.254 Instance Metadata Service.
The operation requires no authentication, no user interaction, and can be executed over the network. The publicly disclosed exploit lowers the barrier to opportunistic abuse against exposed feelcrm-os deployments.
Root Cause
The root cause is missing validation and allow-listing on the url input before it is handed to the cURL request routine. The controller trusts attacker-supplied input to define the request destination, protocol, and path. There is no filtering for internal IP ranges, loopback addresses, link-local addresses, or non-HTTP schemes such as file://, gopher://, or dict:// that cURL may support depending on build options.
Attack Vector
An unauthenticated remote attacker sends a crafted HTTP request to the getCurlData endpoint with a malicious url parameter. The server fetches the specified resource and may return the content in its response. Typical abuse scenarios include scanning internal network ranges, pulling cloud credentials from metadata APIs, interacting with internal admin consoles, and pivoting to blind SSRF chains against databases or caches.
See the VulDB Vulnerability Details and GitHub Issue Tracker for additional technical references. No verified proof-of-concept code is reproduced here.
Detection Methods for CVE-2026-105290
Indicators of Compromise
- Inbound HTTP requests to paths invoking the GoogleControllergetCurlData endpoint containing a url parameter.
- Outbound requests from the feelcrm-os server to RFC1918 addresses, 127.0.0.1, or 169.254.169.254 that do not match normal application behavior.
- Unexpected cURL user-agent traffic originating from the application host toward cloud metadata services.
- Responses from the application containing content retrieved from internal-only URLs.
Detection Strategies
- Review web server access logs for requests to the getCurlData endpoint and inspect the url parameter for internal, loopback, or non-HTTP schemes.
- Correlate inbound application requests with outbound egress from the server to identify unexpected request chains.
- Deploy web application firewall rules that match SSRF payload patterns targeting metadata IPs and private address space.
Monitoring Recommendations
- Alert on any traffic from application servers to 169.254.169.254 or other cloud metadata endpoints unless explicitly expected.
- Monitor PHP process network connections for outbound traffic to private IP ranges originating from feelcrm-os hosts.
- Capture and retain full URL query strings in access logs so SSRF probes using the url parameter are reconstructable.
How to Mitigate CVE-2026-105290
Immediate Actions Required
- Restrict public exposure of feelcrm-os 1.0.0 and place the application behind authenticated access controls or a VPN until a vendor patch is available.
- Block or filter the getCurlData endpoint at the reverse proxy or WAF layer if the functionality is not required for business operations.
- Enforce egress filtering on the application host to deny outbound traffic to RFC1918 ranges, loopback, link-local, and cloud metadata addresses.
- Rotate any cloud instance credentials that may have been exposed through the metadata service if the application runs in a cloud environment.
Patch Information
At the time of publication, the feelec-yishu feelcrm-os project had been notified via the GitHub Issue Tracker but had not responded. No official patch is available. Monitor the GitHub Project Repository and the VulDB CVE Listing for updates.
Workarounds
- Modify the getCurlData function in App/Feelcrm/Index/Controller/GoogleController.class.php to validate the url parameter against a strict allow-list of permitted domains.
- Reject URLs whose resolved IP addresses fall within private, loopback, link-local, or multicast ranges before issuing the cURL request.
- Restrict allowed URL schemes to http and https only, and disable cURL redirects or validate each hop against the allow-list.
- Require IMDSv2 session tokens on AWS instances to limit the impact of SSRF against cloud metadata.
# Example egress filter blocking SSRF targets at the host firewall
iptables -A OUTPUT -d 169.254.169.254 -j REJECT
iptables -A OUTPUT -d 127.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 10.0.0.0/8 -j REJECT
iptables -A OUTPUT -d 172.16.0.0/12 -j REJECT
iptables -A OUTPUT -d 192.168.0.0/16 -j REJECT
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

