dbcve.org
InjectionWeakness · CWE-74

CVE-2026-2533

HIGH · 7.3 CVSS v3.1 Published 2026-02-16
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 flaw has been found in Tosei Self-service Washing Machine 4.02. Impacted is an unknown function of the file /cgi-bin/tosei_datasend.php. Executing a manipulation of the argument adr_txt_1 can lead to command injection. It is possible to launch the attack remotely. The exploit has been published 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 · high confidence

A command injection vulnerability exists in the Tosei Self-service Washing Machine web interface (v4.02). The /cgi-bin/tosei_datasend.php script does not properly sanitize the adr_txt_1 parameter before passing it to system calls, allowing remote attackers to execute arbitrary OS commands.

MitigationSince the vendor is non-responsive and no patch is available, implement compensating controls such as network segmentation to isolate the device, deploy WAF rules to block malicious parameter patterns, and monitor for exploitation attempts. Consider replacing the device if patches remain unavailable.

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 Tosei web interface presence
    Access the device's web interface via its IP address and look for Tosei branding or login page. Check the HTTP response headers or footer for 'Tosei' or 'Self-service Washing Machine' text.
    Affected if The device is a Tosei Self-service Washing Machine with a web management interface accessible on the network
  2. Check web interface version
    Navigate to the main login page or an 'About'/'Status' page on the web interface. Look for a version number displayed, typically in the footer or system information section.
    Affected if The displayed version is 4.02 or falls within uncertain version boundaries around 4.02 (since only v4.02 is explicitly listed as affected)
  3. Verify vulnerable script exists
    Attempt to access the URL path /cgi-bin/tosei_datasend.php on the device's web server. Use a tool like curl: curl -s http://[device-ip]/cgi-bin/tosei_datasend.php
    Affected if The script returns an HTTP 200 response, indicating the file exists and the vulnerable endpoint is present
  4. Confirm adr_txt_1 parameter is accepted
    Send a GET or POST request to /cgi-bin/tosei_datasend.php with the adr_txt_1 parameter (e.g., curl -d 'adr_txt_1=test' http://[device-ip]/cgi-bin/tosei_datasend.php). Observe whether the parameter is processed without error.
    Affected if The parameter is accepted and processed by the script, indicating the command injection entry point is enabled
  5. Review access logs for exploitation attempts
    Check the device's web server access logs or any available logging for requests to /cgi-bin/tosei_datasend.php containing shell metacharacters (like ;, |, &&, backticks) in the adr_txt_1 parameter.
    Affected if Log entries show requests with shell command syntax in the adr_txt_1 parameter, indicating potential exploitation

The environment is affected if it is a Tosei Self-service Washing Machine web interface version 4.02 (or ambiguous versions near 4.02) with the /cgi-bin/tosei_datasend.php script accessible and accepting the adr_txt_1 parameter.

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

Since the vendor is non-responsive and no patch is available, implement compensating controls such as network segmentation to isolate the device, deploy WAF rules to block malicious parameter patterns, and monitor for exploitation attempts. Consider replacing the device if patches remain unavailable.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2533 — 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-2533 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