Skip to main content
CVE-2024-50713VulnerabilityPublished Updated

CVE-2024-50713: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
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:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2024

  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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-50713, organizations should immediately audit their use of SmartAgent v1.1.0 and restrict or disable access to the /tests/interface.php endpoint if possible. 2) Apply input validation and sanitization on the 'id' parameter, ensuring only expected numeric or alphanumeric values are accepted. 3) Use parameterized queries or prepared statements in the backend code to prevent injection. 4) Monitor logs for unusual database query patterns or repeated access attempts to the vulnerable endpoint. 5) Isolate the SmartAgent application behind network segmentation to limit exposure. 6) Prepare an incident response plan in case of exploitation. Organizations should also engage with the vendor for patches or updates and plan to upgrade once fixes are released. Regular backups of databases should be maintained to enable recovery from potential data loss.

Description

SmartAgent v1.1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /tests/interface.php.

References

Community reviews

Loading reviews…