CVE-2024-0988
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 classified as critical was found in Sichuan Yougou Technology KuERP up to 1.0.4. Affected by this vulnerability is the function checklogin of the file /application/index/common.php. The manipulation of the argument App_User_id/App_user_Token leads to improper authentication. The exploit has been disclosed to the public and may be used. The identifier VDB-252253 was 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 critical authentication bypass vulnerability exists in KuERP up to 1.0.4 where the checklogin function in /application/index/common.php fails to properly validate the App_User_id and App_user_Token arguments, allowing attackers to manipulate these parameters to bypass authentication entirely and gain unauthorized access to the ERP system.
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.
-
Identify installed KuERP versionLocate the version file or banner in the KuERP installation directory (common locations include version.php, a version constant in index.php, or the admin panel about page). Compare the version number to the affected range <= 1.0.4.Affected if The installed version is 1.0.4 or lower.
-
Verify vulnerable file existsCheck for the presence of /application/index/common.php in the web root directory of the KuERP installation.Affected if The file /application/index/common.php exists in the application directory.
-
Inspect the checklogin functionOpen /application/index/common.php and locate the checklogin function. Examine whether it performs proper validation on the App_User_id and App_user_Token parameters before granting access.Affected if The checklogin function exists but does not validate App_User_id and App_user_Token parameters before allowing authentication bypass.
-
Test authentication bypass vectorSend a crafted HTTP request to any authenticated endpoint (such as /index.php/Admin/index or similar) with manipulated App_User_id and App_user_Token headers or parameters, observing whether access is granted without valid credentials.Affected if The application grants access when provided with arbitrary or missing App_User_id and App_user_Token values.
A user is affected if their KuERP installation is version 1.0.4 or lower and the checklogin function in /application/index/common.php fails to validate the App_User_id and App_user_Token parameters, allowing unauthenticated access.
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 proper token validation and session authentication in the checklogin function; deploy a WAF as a compensating control; if vendor does not provide a patch, consider alternative ERP solutions or network isolation to limit exposure.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0988 — 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-0988 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