Skip to main content
VulnerabilityPublished

CVE-2024-55517: Polaris FT Intellect Core Banking · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 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

AI-suggested

To mitigate CVE-2024-55517, organizations should implement the following specific measures: 1) Apply vendor patches immediately once available; 2) Until patches are released, restrict access to the /SCGController endpoint to only trusted and necessary authenticated users; 3) Implement strict input validation and sanitization on the groupType parameter to reject or properly escape malicious input; 4) Employ parameterized queries or prepared statements in the backend code to prevent SQL injection; 5) Conduct thorough code reviews and security testing focused on input handling in the Interllect Core Search module; 6) Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts; 7) Enforce strong authentication and credential management to reduce risk of compromised accounts; 8) Segment the network to limit the impact of potential exploitation; 9) Educate staff about the risks of SQL injection and the importance of secure coding practices. These steps will help reduce the attack surface and protect critical banking data until a permanent fix is deployed.

Description

An issue was discovered in the Interllect Core Search in Polaris FT Intellect Core Banking 9.5. Input passed through the groupType parameter in /SCGController is mishandled before being used in SQL queries, allowing SQL injection in an authenticated session.

References

Community reviews

Loading reviews…