CVE-2024-7896
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 vulnerability was found in Tosei Online Store Management System ネット店舗管理システム 4.02/4.03/4.04. It has been rated as critical. Affected by this issue is some unknown functionality of the file /cgi-bin/p1_ftpserver.php. The manipulation of the argument adr_txt leads to command injection. The attack may be launched 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 confidenceCommand injection vulnerability in Tosei Online Store Management System (versions 4.02/4.03/4.04) in the /cgi-bin/p1_ftpserver.php script. The 'adr_txt' parameter is not properly sanitized before being used in a system command, allowing remote attackers to execute arbitrary OS commands.
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= 4.0.2= 4.0.3= 4.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Tosei Online Store Management System is installedLook for the application in the web root directory, typically under /var/www/html or C:\inetpub\wwwroot, or search for files containing 'Tosei' or 'Online Store' in their metadataAffected if The application is present on the system
-
Check the installed versionSearch for version files, about pages, or admin panels that display the software version. Common locations include /about.html, /admin/version.php, or a config file in the application rootAffected if The version is exactly 4.0.2, 4.0.3, or 4.0.4
-
Confirm the vulnerable script existsCheck if the file /cgi-bin/p1_ftpserver.php exists in the web rootAffected if The file p1_ftpserver.php exists in the cgi-bin directory
-
Verify CGI execution is enabledCheck the web server configuration (Apache httpd.conf, Nginx config, or IIS handler mappings) to confirm PHP files in cgi-bin are executed as CGI scripts rather than served as static contentAffected if PHP scripts in cgi-bin are configured to execute as CGI
The system is affected if Tosei Online Store Management System version 4.0.2, 4.0.3, or 4.0.4 is installed with the p1_ftpserver.php script present and CGI execution enabled for that location.
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 dataSince the vendor did not respond, implement input validation/sanitization on the adr_txt parameter in p1_ftpserver.php, or deploy a WAF rule to block malicious input patterns. Consider upgrading or replacing the product if no patch becomes available.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7896 — 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-2024-7896 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