CVE-2024-8941
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 · uneditedPath traversal vulnerability in Scriptcase version 9.4.019, in /scriptcase/devel/compat/nm_edit_php_edit.php (in the “subpage” parameter), which allows unauthenticated remote users to bypass SecurityManager's intended restrictions and list and/or read a parent directory via a “/...” or directly into a path used in the POST parameter “field_file” by a web application.
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 confidencePath traversal vulnerability in Scriptcase 9.4.019 in the nm_edit_php_edit.php file allows unauthenticated remote users to bypass SecurityManager restrictions and access parent directories via the 'subpage' GET parameter using '/...' sequences or the 'field_file' POST parameter.
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= 9.4.019CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Locate the affected PHP fileSearch the web server document root for nm_edit_php_edit.php. Common paths include /scriptcase/nm_edit_php_edit.php or /app/nm_edit_php_edit.php depending on installation.Affected if The file nm_edit_php_edit.php exists in the web-accessible directory
-
Confirm Scriptcase versionCheck the Scriptcase installation for version information. Typically found in a version file, about page, or the scriptcase.ini configuration file.Affected if The installed version is exactly 9.4.019
-
Verify web accessibility of the affected fileAttempt an HTTP request to the nm_edit_php_edit.php file endpoint without authentication credentials.Affected if The file is accessible via HTTP/HTTPS without requiring authentication
-
Test for vulnerable parameter handlingSend a GET request to nm_edit_php_edit.php with a crafted 'subpage' parameter containing path traversal sequences such as '/..' or '/...' to test if parent directory access is possible.Affected if The application accepts and processes '../' or '/...' sequences in the 'subpage' parameter without rejecting them
-
Check SecurityManager configurationReview the Scriptcase SecurityManager settings to confirm whether the nm_edit_php_edit.php file is supposed to be protected by directory access controls.Affected if SecurityManager restrictions exist but can be bypassed via the path traversal in this file
If Scriptcase version 9.4.019 is installed AND the nm_edit_php_edit.php file is web-accessible AND the application accepts path traversal sequences in the 'subpage' or 'field_file' parameters, then the environment is affected by CVE-2024-8941.
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 dataUpgrade to a patched version of Scriptcase; until then, restrict access to the affected PHP file via web server configuration or deploy input validation to block '../' sequences.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8941 — 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-8941 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