Skip to main content

DivvyDrive CVE-2026-5220

| EUVDEUVD-2026-41008 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-07-01 TR-CERT GHSA-rr2x-7r28-45fw
6.4
CVSS 3.1 · Vendor: TR-CERT
Share

Severity by source

Vendor (TR-CERT) PRIMARY
6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI
5.4 MEDIUM

Stored XSS requires victim to view the injected page (UI:R); PR:L reflects required low-privilege account; S:C and C:L/I:L capture cross-boundary session impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (TR-CERT).

CVSS VectorVendor: TR-CERT

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

1
Analysis Generated
Jul 01, 2026 - 14:56 vuln.today

DescriptionCVE.org

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in DivvyDrive Information Technologies Inc. DivvyDrive allows Stored XSS.

This issue affects DivvyDrive: from 4.8.2.23 before v.4.8.3.1.

AnalysisAI

Stored cross-site scripting in DivvyDrive (versions 4.8.2.23 through before 4.8.3.1) allows authenticated low-privilege attackers to inject persistent malicious scripts that execute in the browsers of other users who view affected pages. The CVSS scope change (S:C) reflects that injected scripts operate outside the application's security boundary, enabling session hijacking or credential theft against higher-privileged victims such as administrators. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the low attack complexity and cross-scope impact make this a meaningful lateral escalation risk within DivvyDrive deployments.

Technical ContextAI

DivvyDrive is a web-based application developed by DivvyDrive Information Technologies Inc. (a Turkish vendor). The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically the stored (persistent) variant, meaning user-supplied input is written to a data store and later rendered into HTML responses served to other users without proper output encoding or sanitization. The CVSS scope-change metric (S:C) is appropriate here because injected JavaScript executes in the victim's browser context, outside the vulnerable application's own trust boundary, enabling the script to access session tokens or perform authenticated actions on behalf of the victim. CPE: cpe:2.3:a:divvydrive_information_technologies_inc.:divvydrive:*:*:*:*:*:*:*:*.

RemediationAI

Upgrade DivvyDrive to version 4.8.3.1 or later, which resolves this stored XSS vulnerability per the TR-CERT advisory at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0475. If immediate patching is not feasible, restrict write access to DivvyDrive input fields to the minimum required set of trusted users, reducing the pool of accounts that could inject payloads. Deploying a strict Content Security Policy (CSP) header that disallows inline scripts can limit the exploitability of any stored payload, though this may break legitimate application functionality and requires testing. Additionally, audit stored content for existing script-like patterns and enable logging of content submission events from low-privilege accounts to detect exploitation attempts.

Share

CVE-2026-5220 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy