Skip to main content
VulnerabilityPublished

CVE-2026-4955: Shenzhen Ruiming Technology Streamax Crocus · SQL Injection

Affects Shenzhen Ruiming Technology Streamax CrocusSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% 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:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Shenzhen Ruiming TechnologyStreamax CrocusAffected
  • =1.3.44
Fixed in–

AI-suggested

To mitigate CVE-2026-4955, organizations should implement the following specific measures: 1) Apply strict input validation and sanitization on the VehicleID parameter at the application or web server level to block malicious SQL payloads. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting /OperateStatistic.do. 3) Restrict network access to the Streamax Crocus management interface to trusted IP addresses and internal networks only, reducing exposure to remote attackers. 4) Monitor database query logs and application logs for unusual or suspicious activity indicative of SQL injection attempts. 5) Isolate the database server from direct internet access and enforce least privilege principles on database accounts used by the application. 6) If possible, upgrade to a newer, patched version of the software once available or consider alternative solutions if vendor support is lacking. 7) Conduct regular security assessments and penetration testing focused on injection vulnerabilities. 8) Maintain offline backups of critical data to enable recovery in case of data tampering or loss. These targeted actions go beyond generic advice and address the specific attack vector and operational context of the vulnerability.

Description

A vulnerability was found in Shenzhen Ruiming Technology Streamax Crocus 1.3.44. This impacts an unknown function of the file /OperateStatistic.do. The manipulation of the argument VehicleID results in sql injection. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…