Skip to main content
CVE-2024-28421VulnerabilityPublished Updated

CVE-2024-28421: razor · n/a

Affects razorSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% 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 25 Mar 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-25.

What to do

Affected software

ProductAffectedFixed in
GitHubcobub/razorpkg:github/cobub/razorOther threatsAffected
  • =0.8.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate verification of the Razor version in use is essential; if running version 0.8.0, restrict external access to the affected application until a patch or fix is available. 2. Implement Web Application Firewall (WAF) rules to detect and block SQL Injection attempts targeting the ChannelModel::updateapk method, focusing on suspicious input patterns. 3. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters processed by the updateapk method, employing prepared statements or parameterized queries to prevent injection. 4. Monitor application logs for unusual database query patterns or errors indicative of injection attempts. 5. Apply the principle of least privilege to database accounts used by the application, limiting permissions to only what is necessary to reduce potential damage. 6. Stay updated with vendor advisories for official patches or updates addressing this vulnerability and apply them promptly once available. 7. Perform regular security assessments and penetration testing focused on injection vulnerabilities to identify and remediate similar issues proactively. 8. Educate development teams on secure coding practices to prevent future injection flaws.

Description

SQL Injection vulnerability in Razor 0.8.0 allows a remote attacker to escalate privileges via the ChannelModel::updateapk method of the channelmodle.php

References

Community reviews

Loading reviews…