dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4956

HIGH · 7.3 CVSS v3.1 Published 2026-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was detected in Shenzhen Ruiming Technology Streamax Crocus 1.3.44. The affected element is an unknown function of the file /DevicePrint.do?Action=ReadTask of the component Parameter Handler. The manipulation of the argument State results in sql injection. The attack can be launched remotely. The exploit is now public and may 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 · moderate confidence

SQL injection vulnerability in Streamax Crocus 1.3.44's DevicePrint.do Parameter Handler. The 'State' argument in the ReadTask action fails to sanitize input properly, allowing remote attackers to inject malicious SQL queries. The exploit is publicly available and requires no authentication.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in the DevicePrint.do ReadTask function. Implement strict input validation on the State parameter and all user-supplied values before constructing database queries.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Streamax Crocus is deployed
    Review your software inventory or application directory for the Streamax Crocus web application. Check for the presence of the DevicePrint.do endpoint by examining web server logs or accessing the application's URL structure.
    Affected if Streamax Crocus software is present in the environment
  2. Determine the installed Crocus version
    Locate the application version information - check the application web interface for a version display, review deployment manifests, or inspect the application's compiled files or configuration for a version string. Compare the found version to 1.3.44.
    Affected if The installed version is 1.3.44 or falls within the 1.3.x branch where the vulnerability exists
  3. Verify DevicePrint.do endpoint is exposed
    Attempt to access the DevicePrint.do endpoint via HTTP/HTTPS request, or review web server access logs for any requests to paths containing DevicePrint.do. This is the component that contains the vulnerable ReadTask action.
    Affected if The DevicePrint.do endpoint is accessible and responds to requests
  4. Check if ReadTask action is enabled
    Inspect application configuration files or routing definitions to determine if the ReadTask action within DevicePrint.do is active. This action processes the State parameter.
    Affected if The ReadTask action is enabled and processes user-supplied parameters including State
  5. Inspect input handling for State parameter
    Examine the application source code or decompiled classes related to DevicePrint.do, specifically the ReadTask function, to see how the State parameter is processed before being used in database queries.
    Affected if The State parameter is used in dynamic SQL queries without proper sanitization or parameterized queries

A user is affected if Streamax Crocus version 1.3.44 is running with the DevicePrint.do ReadTask action accessible and the State parameter processed without parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements in the DevicePrint.do ReadTask function. Implement strict input validation on the State parameter and all user-supplied values before constructing database queries.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4956 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4956 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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