CVE-2025-15129
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 flaw has been found in ChenJinchuang Lin-CMS-TP5 up to 0.3.3. This vulnerability affects the function Upload of the file application/lib/file/LocalUploader.php of the component File Upload Handler. Executing manipulation of the argument File can lead to code injection. The attack can be executed remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 confidenceA code injection vulnerability exists in the Upload function of LocalUploader.php in Lin-CMS-TP5 up to version 0.3.3. The file upload handler fails to properly validate or sanitize uploaded files, allowing an attacker to manipulate the File argument to inject and execute arbitrary code on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Lin-CMS-TP5 installationLocate the Lin-CMS-TP5 application directory - typically installed via composer or git clone. Look for the project structure containing app and application directories common to ThinkPHP5 applications.Affected if Lin-CMS-TP5 is not present in the environment
-
Identify the installed versionCheck the version file or composer.json in the project root for the Lin-CMS-TP5 version number. Compare against 0.3.3 - any version 0.3.3 or lower is affected.Affected if The installed version is 0.3.3 or lower
-
Locate LocalUploader.phpSearch for the file LocalUploader.php within the application - typically in application or app directories under paths like api, common, or plugin folders related to upload functionality.Affected if LocalUploader.php exists and is part of the active application code
-
Verify upload functionality is accessibleCheck if there are active routes or endpoints that map to the Upload function in LocalUploader.php - look in route configuration files or examine the controller/method that calls the upload handler.Affected if An upload endpoint using LocalUploader is accessible and operational
-
Inspect upload validation configurationExamine the Upload function in LocalUploader.php for file validation logic - look for checks on file type, extension, MIME type, or content verification before file processing occurs.Affected if No file type whitelist or content validation is implemented in the upload handler
A user is affected if they are running Lin-CMS-TP5 version 0.3.3 or lower with the LocalUploader.php upload functionality accessible and lacking proper file validation.
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 file type validation (whitelist approach), sanitize filenames, store uploaded files outside the web root, and disable script execution in the upload directory. Also verify the file content/magic bytes rather than relying solely on file extensions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15129 — 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-2025-15129 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