CVE-2026-4955
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA SQL injection vulnerability exists in Streamax Crocus 1.3.44 in the /OperateStatistic.do endpoint where the VehicleID parameter is not properly sanitized before being used in SQL queries. This allows remote attackers to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Streamax Crocus installation and versionLocate the application installation directory or check the web interface for the version number. Common paths include /opt/streamax/crocus or check the application's about/help page for version 1.3.44.Affected if The installed version is Streamax Crocus 1.3.44 exactly, or falls within the 1.3.x range prior to the patched version.
-
Verify /OperateStatistic.do endpoint is exposedAccess the URL https://<your-server>/OperateStatistic.do in a browser or via curl to confirm the endpoint is reachable and responding.Affected if The endpoint returns a valid HTTP response (200 OK) indicating it is actively handling requests.
-
Identify if VehicleID parameter is in useSubmit a GET or POST request to /OperateStatistic.do with a test VehicleID parameter (e.g., ?VehicleID=123) and observe if the parameter is processed by the application.Affected if The application accepts and processes the VehicleID parameter without rejecting it as invalid input.
-
Test for SQL injection vulnerabilitySend a malformed VehicleID value designed to trigger SQL syntax errors, such as VehicleID=1' OR '1'='1 or VehicleID=1;-- and observe the application response for SQL error messages or unexpected behavior.Affected if The application returns database error messages (e.g., MySQL syntax error, ODBC error) or exhibits unusual behavior indicating SQL commands may be executed.
You are affected if Streamax Crocus version 1.3.44 is installed, the /OperateStatistic.do endpoint is accessible, and the VehicleID parameter accepts input that triggers SQL errors or unexpected behavior, indicating lack of parameterized query handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries or prepared statements for the VehicleID parameter in /OperateStatistic.do to prevent SQL injection. If vendor patch is unavailable, consider web application firewall as interim control.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4955 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data