CVE-2026-4910
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 security vulnerability has been detected in Shenzhen Ruiming Technology Streamax Crocus up to 1.3.44. Affected is an unknown function of the file /RemoteFormat.do of the component Endpoint. Such manipulation of the argument State leads to sql injection. It is possible to launch 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.
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 confidenceSQL injection vulnerability in Shenzhen Ruiming Technology Streamax Crocus web application (versions up to 1.3.44) in the /RemoteFormat.do endpoint. The State parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries and potentially access, modify, or delete database contents.
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.
-
Identify Streamax Crocus installationLocate the Streamax Crocus web application installation directory or check running web services for the application. Look for files or services associated with 'Streamax' or 'Crocus'.Affected if The Streamax Crocus web application is present in the environment.
-
Determine installed versionCheck the application's version information, typically found in the application metadata, about page, or configuration files within the installation directory. Compare this version to 1.3.44.Affected if The installed version is 1.3.44 or any earlier version.
-
Verify /RemoteFormat.do endpoint accessibilityCheck if the web server exposes the /RemoteFormat.do endpoint by attempting to access it via HTTP/HTTPS (e.g., GET request to http[s]://[host]/RemoteFormat.do).Affected if The endpoint responds and is accessible from the network.
-
Check State parameter for SQL injection susceptibilitySend a test request to /RemoteFormat.do with the State parameter containing SQL syntax (e.g., State=') and observe the response for SQL errors, unexpected behavior, or differences from normal responses. Common indicators include SQL error messages in the response body.Affected if The application returns SQL error messages or exhibits unusual behavior when special characters are passed to the State parameter.
If Streamax Crocus version 1.3.44 or lower is installed and the /RemoteFormat.do endpoint is accessible, the environment is likely affected by this SQL injection vulnerability.
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 dataApply vendor patch when available. Until then, implement input validation and parameterized queries on the State parameter, and restrict network access to the affected endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4910 — 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-4910 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