PACKETSTORM 8.5 HIGH

📄 SocialEngine 7.8.0 Server-Side Request Forgery_PACKETSTORM:219704

8.5 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Description

SocialEngine versions 7.8.0 and below suffer from a blind server-side request forgery vulnerability. User input passed through the uri request parameter to the /core/link/preview endpoint is not properly sanitized before being used as URL to send an...
Visit Original Source

Basic Information

ID PACKETSTORM:219704
Published Apr 23, 2026 at 00:00

Affected Product

Affected Versions ---------------------------------------------------------------------
SocialEngine <= 7.8.0 Blind Server-Side Request Forgery Vulnerability
---------------------------------------------------------------------


[-] Software Link:

https://socialengine.com


[-] Affected Versions:

Versions 7.8.0, 7.7.0, and likely prior versions.


[-] Vulnerability Description:

User input passed through the "uri" request parameter to the
/core/link/preview endpoint is not properly sanitized before being
used as URL to send an HTTP request from the web server. This can be
exploited by remote, authenticated attackers to carry out blind
Server-Side Request Forgery (SSRF) attacks by using URLs like the
following:

https://[socialengine]/core/link/preview/format/json?uri=http://localhost:3306/


[-] Solution:

No official solution is currently available.


[-] Disclosure Timeline:

[02/02/2026] - Vulnerability confirmed on version 7.7.0

[02/02/2026] - Vendor notified

[09/02/2026] - Vendor response stating "We are currently validating
your report... If this issue is confirmed, we will prioritize
appropriate fixes and include them in an upcoming update."

[27/02/2026] - Vendor released version 7.8.0, but the vulnerability is
still not fixed

[02/03/2026] - Vendor contacted again

[09/03/2026] - Vendor response stating "We will check and update you."

[23/03/2026] - Vendor notified about 60-day disclosure deadline policy

[25/03/2026] - Vendor response stating "Regarding this issue, we were
unable to fully understand the concern. Could you please provide more
detailed information or steps to reproduce the issue?"

[25/03/2026] - Vendor was provided with more details and guidance on
how to fix the vulnerability

[03/04/2026] - Reached 60-day disclosure deadline, still no official solution

[21/04/2026] - CVE identifier requested

[22/04/2026] - CVE identifier assigned

[23/04/2026] - Public disclosure


[-] CVE Reference:

CVE-2026-41461 has been assigned to this vulnerability.


[-] Credits:

Vulnerability discovered by Egidio Romano.


[-] Original Advisory:

https://karmainsecurity.com/KIS-2026-07

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.