CVE-2025-11910VulnerabilityPublished 17 Oct 2025

CVE-2025-11910: Shenzhen Ruiming Technology Streamax Crocus · SQL Injection

Affects Shenzhen Ruiming Technology Streamax CrocusSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Shenzhen Ruiming Technology Streamax Crocus	Affected =1.3.40	Fixed in–

AI-suggested

1. Immediately restrict network access to the /MemoryState.do?Action=Query endpoint using firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Deploy and configure Web Application Firewalls (WAFs) with SQL injection detection and prevention capabilities to block malicious payloads targeting the orderField parameter. 3. Conduct thorough input validation and sanitization on all user-supplied parameters, especially orderField, if custom modifications or patches are possible. 4. Monitor application logs and network traffic for unusual query patterns or error messages indicative of SQL injection attempts. 5. If possible, isolate the Streamax Crocus system from critical networks until a vendor patch or official fix is available. 6. Engage with Shenzhen Ruiming Technology for updates and request a security patch or mitigation guidance. 7. Review and enhance database user privileges to follow the principle of least privilege, limiting the damage potential of injected queries. 8. Prepare incident response plans specific to database compromise scenarios involving Streamax Crocus. 9. Consider alternative or additional surveillance solutions if patching is delayed or vendor support remains absent.

Description

A security vulnerability has been detected in Shenzhen Ruiming Technology Streamax Crocus 1.3.40. This affects the function Query of the file /MemoryState.do?Action=Query. The manipulation of the argument orderField leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the SQL injection vulnerability in Streamax Crocus poses risks to data confidentiality, integrity, and availability. Exploitation could lead to unauthorized data disclosure, including sensitive surveillance data or operational metadata, potentially violating GDPR and other data protection regulations. Integrity of stored data could be compromised, affecting the reliability of surveillance records or system logs. Availability impacts could disrupt surveillance operations, critical in sectors such as transportation, public safety, or utilities. Given the remote exploitability without authentication, attackers could leverage this vulnerability to gain footholds in networks, escalate privileges, or move laterally. The absence of vendor patches and public exploit code increases urgency for defensive measures. Organizations relying on Streamax Crocus for security monitoring or operational control should assess exposure and implement compensating controls to prevent data breaches or operational disruptions.

Summary

CVE-2025-11910 is a SQL injection vulnerability identified in version 1.3.40 of Shenzhen Ruiming Technology's Streamax Crocus software. The vulnerability resides in the Query function accessed via the /MemoryState.do?Action=Query endpoint, specifically through the orderField parameter. This parameter is not properly sanitized or validated, allowing an attacker to inject arbitrary SQL code remotely without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 5.3, indicating a medium severity level, with an attack vector of network (remote), low attack complexity, no privileges required, and no user interaction needed. The impact vector includes low confidentiality, integrity, and availability impacts, suggesting partial but not full compromise potential. The vendor was notified early but has not responded or released patches, and no known exploits are currently observed in the wild. The vulnerability could be exploited to extract sensitive data, modify database contents, or disrupt service availability by manipulating backend database queries. This type of injection flaw is critical in web applications interfacing with databases, especially in surveillance or monitoring systems like Streamax Crocus, which may handle sensitive video or metadata. The lack of vendor response increases the risk profile, requiring organizations to implement immediate mitigations and monitoring.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2025, 20:01 UTC

Technical details

References

Community reviews

Related threats