CVE-2024-10749
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 critical, was found in ThinkAdmin up to 6.1.67. Affected is the function script of the file /app/admin/controller/api/Plugs.php. The manipulation of the argument uptoken leads to deserialization. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. 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 · moderate confidenceThinkAdmin versions up to 6.1.67 contain a deserialization vulnerability in the script function of /app/admin/controller/api/Plugs.php. The uptoken parameter is not properly validated before being passed to a deserialization function, allowing remote attackers to craft malicious serialized payloads that execute arbitrary code upon unserialization.
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>= 6.0, <= 6.1.67CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 ThinkAdmin installation and versionLocate the ThinkAdmin installation directory and find the version file or bootstrap file that contains the version number. Common locations include a version.php file, composer.json, or the main application entry point.Affected if The installed version is between 6.0 and 6.1.67 inclusive.
-
Verify vulnerable file existsInspect the file /app/admin/controller/api/Plugs.php in the ThinkAdmin installation directory. Check for the presence of a method that handles the uptoken parameter.Affected if The file exists and contains code that processes the uptoken parameter.
-
Check for unsafe deserialization usageSearch within Plugs.php for unserialize() calls or similar PHP deserialization functions that process the uptoken parameter without proper validation.Affected if The code passes the uptoken parameter directly to a deserialization function without validation.
-
Determine network exposureCheck if the ThinkAdmin application is accessible over the network, particularly the /app/admin/controller/api/Plugs.php endpoint. Verify whether authentication or network restrictions are in place.Affected if The vulnerable endpoint is accessible without authentication or adequate network segmentation.
-
Review access logs for exploitation attemptsExamine web server access logs for requests to the Plugs.php endpoint containing the uptoken parameter. Look for base64-encoded or serialized data patterns in the parameter values.Affected if Suspicious requests with encoded or serialized data in the uptoken parameter are present in logs.
A user is affected if they are running ThinkAdmin version 6.0 through 6.1.67, the vulnerable Plugs.php file exists with unsafe deserialization logic, and the endpoint is accessible without proper validation controls.
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.
dbcve · scopedUpgrade to a patched version of ThinkAdmin. If upgrade is not immediately possible, implement input validation on the uptoken parameter and replace PHP unserialize() with safer alternatives such as JSON decoding, or implement allowlist-based validation for deserialized classes.
ThinkAdmin > 6.1.67 (latest stable release from official repository)
- Check current ThinkAdmin version using composer show or the application's version indicator
- Upgrade to a version higher than 6.1.67 - check the official ThinkAdmin repository (github.com/zoujingli/ThinkAdmin) for the latest stable release
- After upgrading, verify the Plugs.php file has been updated and the script function no longer uses untrusted deserialization on the uptoken parameter
- If immediate upgrade is not possible, restrict network access to the /app/admin/controller/api/Plugs.php endpoint using web server configuration (e.g., Nginx/Apache ACL rules)
- Monitor for any unauthorized access attempts to the affected endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- 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-10749 — 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-10749 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