dbcve.org
Online Store Management SystemApplication · Tosei Corporation

CVE-2026-2944

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 security flaw has been discovered in Tosei Online Store Management System ネット店舗管理システム 1.01. Affected is the function system of the file /cgi-bin/monitor.php of the component HTTP POST Request Handler. Performing a manipulation of the argument DevId results in os command injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. 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 critical OS command injection vulnerability exists in Tosei Online Store Management System 1.01's /cgi-bin/monitor.php script. The DevId parameter passed via HTTP POST is directly used in a system() function call without sanitization, allowing remote attackers to execute arbitrary operating system commands.

MitigationImmediately restrict access to /cgi-bin/monitor.php via network-level controls or web server configuration until input validation and proper escaping can be implemented. Replace the system() call with safer alternatives or implement parameterized command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Store Management SystemApplication
Affected:= 1.01

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Online Store Management System installation
    Search the system for files or directories indicating Tosei Online Store Management System, such as CGI-bin folders, web server document roots, or application directories containing 'tosei' or 'online store' in the path
    Affected if The software is found installed on the system
  2. Verify the installed version is 1.01
    Locate version information for the Tosei installation - check for version files, headers in PHP files, or application metadata that indicates version 1.01
    Affected if The version is confirmed as 1.01
  3. Check for the presence of monitor.php in CGI-bin
    Locate the CGI-bin directory within the Tosei web application root and verify if monitor.php file exists
    Affected if monitor.php exists in the CGI-bin directory
  4. Confirm network accessibility of monitor.php
    Verify that the monitor.php script is accessible over HTTP/HTTPS from the network - this is required for remote exploitation
    Affected if The script is accessible via HTTP/HTTPS from a network perspective
  5. Inspect DevId parameter handling in monitor.php
    Open monitor.php and locate the code handling the DevId POST parameter - look for direct passage to system(), exec(), or similar shell execution functions without visible sanitization
    Affected if The DevId parameter is passed directly to a system() call without input validation or escaping

The environment is affected if Tosei Online Store Management System version 1.01 is installed, monitor.php exists in CGI-bin, and the DevId parameter is used in a system() call without sanitization, especially if the script is network-accessible.

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

Immediately restrict access to /cgi-bin/monitor.php via network-level controls or web server configuration until input validation and proper escaping can be implemented. Replace the system() call with safer alternatives or implement parameterized command execution.

Fix this in Online Store Management System 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-2944 — 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-2944 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