Skip to main content
VulnerabilityPublished

CVE-2025-4568: Trol InterMedia 2ClickPortal · SQL Injection

Affects Trol InterMedia 2ClickPortalSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Trol InterMedia 2ClickPortalAffected
  • =0
Fixed in–

AI-suggested

Given the critical nature of CVE-2025-4568, European organizations should prioritize immediate mitigation steps beyond generic advice: 1) Implement strict input validation and sanitization on the 'changes__reference_id' parameter, employing parameterized queries or prepared statements to prevent SQL injection. 2) If source code access is available, conduct a thorough code review of all input handling related to database queries in 2ClickPortal. 3) Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting this parameter as an interim protective measure. 4) Monitor application logs and network traffic for anomalous patterns indicative of blind SQL injection attempts. 5) Engage with Trol InterMedia for patches or updates; if none are available, consider temporary disabling or restricting access to vulnerable endpoints. 6) Conduct penetration testing focused on SQL injection vectors to validate the effectiveness of mitigations. 7) Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

Improper neutralization of input provided by an unauthorized user into changes__reference_id parameter in URL allows for boolean-based Blind SQL Injection attacks.

References

Community reviews

Loading reviews…