2025-12-04
[email protected]
6.1
CVSS 3.1
Share
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None
Lifecycle Timeline
5
Patch Released
Mar 31, 2026 - 21:13 nvd
Patch available
EUVD ID Assigned
Mar 15, 2026 - 16:35 euvd
EUVD-2025-201283
Analysis Generated
Mar 15, 2026 - 16:35 vuln.today
PoC Detected
Dec 18, 2025 - 20:24 vuln.today
Public exploit code
CVE Published
Dec 04, 2025 - 20:16 nvd
MEDIUM 6.1
Description
Alinto Sogo 5.12.3 is vulnerable to Cross Site Scripting (XSS) via the theme parameter.
Analysis
Alinto Sogo 5.12.3 is vulnerable to Cross Site Scripting (XSS) via the theme parameter.
Technical Context
Cross-site scripting (XSS) allows injection of client-side scripts into web pages viewed by other users due to insufficient output encoding.
Affected Products
Affected products: Alinto Sogo
Remediation
Encode all user-supplied output contextually (HTML, JS, URL). Implement Content Security Policy (CSP) headers. Use HTTPOnly and Secure cookie flags.
Priority Score
51
Low
Medium
High
Critical
KEV: 0
EPSS: +0.0
CVSS: +30
POC: +20
Vendor Status
Ubuntu
Priority: Mediumsogo
| Release | Status | Version |
|---|---|---|
| xenial | needs-triage | - |
| bionic | needs-triage | - |
| focal | needs-triage | - |
| jammy | needs-triage | - |
| noble | DNE | - |
| questing | needs-triage | - |
| upstream | needs-triage | - |
| plucky | ignored | end of life, was needs-triage |
Debian
Bug #1121952sogo
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye | fixed | 5.0.1-4+deb11u3 | - |
| bullseye (security) | fixed | 5.0.1-4+deb11u3 | - |
| bookworm | fixed | 5.8.0-2+deb12u1 | - |
| trixie | fixed | 5.12.1-3+deb13u1 | - |
| forky, sid | fixed | 5.12.4-1.2 | - |
| (unstable) | fixed | 5.12.4-1.2 | - |
Share
External POC / Exploit Code
Leaving vuln.today
Destination URL
POC code from unknown sources may be malicious, contain backdoors, or be fake.
Always review and test exploit code in a safe, isolated environment (VM/sandbox).
Verify the source reputation and cross-reference with known databases (Exploit-DB, GitHub Security).
EUVD-2025-201283