dbcve.org
Online Store Management SystemApplication · Tosei Corporation

CVE-2024-7897

HIGH · 8.8 CVSS v3.1 Published 2024-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 classified as critical has been found in Tosei Online Store Management System ネット店舗管理システム 4.02/4.03/4.04. This affects an unknown part of the file /cgi-bin/tosei_kikai.php. The manipulation of the argument kikaibangou leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. NOTE: 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

Command injection vulnerability in Tosei Online Store Management System (versions 4.02/4.03/4.04) in the /cgi-bin/tosei_kikai.php script. The kikaibangou parameter is not properly sanitized before being passed to system commands, allowing remote attackers to execute arbitrary OS commands. The exploit is publicly available and remotely exploitable.

MitigationImplement strict input validation on the kikaibangou parameter to disallow any shell metacharacters, or disable the vulnerable tsei_kikai.php script if not business-critical until a vendor patch is available. Consider deploying a WAF as a compensating control.

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:= 4.0.2= 4.0.3= 4.0.4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the vulnerable script
    Check if the file /cgi-bin/tosei_kikai.php exists on the web server by reviewing the web root directory structure or using file system access commands such as 'ls -la /cgi-bin/tosei_kikai.php' or directory listing tools.
    Affected if The script file exists in the cgi-bin directory and is accessible via the web server.
  2. Identify the installed version
    Review system documentation, version files, or admin panels for the Tosei Online Store Management System version number. Compare the installed version against the affected range: versions 4.0.2, 4.0.3, and 4.0.4.
    Affected if The installed version matches 4.0.2, 4.0.3, or 4.0.4.
  3. Verify web server exposure
    Confirm the /cgi-bin/tosei_kikai.php script is reachable via HTTP/HTTPS requests by attempting to access the URL or reviewing web server access logs and configuration for CGI script mappings.
    Affected if The script is publicly accessible or accessible to untrusted users via the web server.
  4. Check for the kikaibangou parameter usage
    Examine the tosei_kikai.php source code to determine if the 'kikaibangou' parameter is processed and passed to system commands without proper sanitization. Look for functions like exec, system, passthru, or shell_exec used with the parameter.
    Affected if The code passes the kikaibangou parameter directly to shell execution functions without input validation.

The environment is affected if the Tosei Online Store Management System versions 4.0.2, 4.0.3, or 4.0.4 are installed, the /cgi-bin/tosei_kikai.php script is accessible, and the kikaibangou parameter flows to system commands without sanitization.

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

Implement strict input validation on the kikaibangou parameter to disallow any shell metacharacters, or disable the vulnerable tsei_kikai.php script if not business-critical until a vendor patch is available. Consider deploying a WAF as a compensating control.

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-2024-7897 — 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-2024-7897 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