CVE-2026-41461: SocialEngine · Server-Side Request Forgery
Affects SocialEngineSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium.
Data as of 12 Nov 2026, 01:05 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.5 |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SocialEngine SocialEngine | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor advisory for updates. In the meantime, restrict access to the vulnerable endpoint to trusted users and consider network-level controls to limit outbound HTTP requests from the server to untrusted destinations.
Description
SocialEngine versions 7.8.0 and earlier have a server-side request forgery (SSRF) vulnerability in the /core/link/preview endpoint. Authenticated attackers can supply arbitrary URLs via the uri parameter, which is not properly sanitized, causing the server to make HTTP requests to attacker-controlled or internal network addresses. This can lead to internal network enumeration and access to otherwise inaccessible services.