CVE-2024-0989
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, which was classified as problematic, has been found in Sichuan Yougou Technology KuERP up to 1.0.4. Affected by this issue is the function del_sn_db of the file /application/index/controller/Service.php. The manipulation of the argument file leads to path traversal: '../filedir'. The exploit has been disclosed to the public and may be used. VDB-252254 is the identifier assigned to this vulnerability. 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 confidenceA path traversal vulnerability in KuERP up to v1.0.4 allows attackers to manipulate the 'file' argument in the del_sn_db function within /application/index/controller/Service.php. By using '../filedir' sequences, attackers can traverse directories and access or delete files outside the intended directory. The public exploit availability and CVSS 9.8 indicate this is likely exploitable without authentication.
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<= 1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm KuERP installationLocate the KuERP application directory. Check for the presence of the /application/index/controller/Service.php file which contains the vulnerable function.Affected if KuERP is installed and Service.php exists at /application/index/controller/Service.php
-
Check KuERP versionInspect version files or configuration within the KuERP installation directory. Common locations include a version.php file, composer.json, or a config file displaying the version number.Affected if The installed version is 1.0.4 or lower (any version <= 1.0.4)
-
Locate vulnerable function codeOpen /application/index/controller/Service.php and search for the 'del_sn_db' function definition.Affected if The del_sn_db function exists in Service.php and accepts a 'file' parameter without proper path traversal validation
-
Verify path traversal vulnerability patternExamine the del_sn_db function code to confirm it uses the 'file' parameter directly in file operations (such as file_exists, unlink, or file operations) without sanitizing '../' sequences or applying basename().Affected if The function uses the file parameter directly in file operations without validating for '../' path traversal sequences
-
Check web server exposureVerify that the Service.php controller is accessible via the web server hosting the KuERP application.Affected if The KuERP web interface is publicly or internally accessible and the Service controller endpoint can be reached
A user is affected if they have KuERP version 1.0.4 or lower installed with the Service.php file present and the del_sn_db function accessible without proper path traversal validation on the file parameter.
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 dataImplement strict input validation on the file parameter to reject path traversal sequences (../ and similar). Consider using basename() to extract only the filename and validating against an allowed directory whitelist.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0989 — 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-0989 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