CVE-2023-30264
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 · uneditedCLTPHP <=6.0 is vulnerable to Unrestricted Upload of File with Dangerous Type via application/admin/controller/Template.php:update.
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 confidenceCLTPHP version 6.0 and below contains an unrestricted file upload vulnerability in the Template controller's update function (application/admin/controller/Template.php). The application fails to properly validate uploaded file types, allowing attackers to upload dangerous file types (such as executable PHP scripts) which could lead to remote code execution.
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.0CVSS 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 CLTPHP versionLocate the version file or composer.json in your CLTPHP installation and compare the version number to the affected range (<= 6.0)Affected if The installed version is 6.0 or lower
-
Verify vulnerable file existsCheck if the file application/admin/controller/Template.php exists in your installationAffected if The file exists and contains an update function handling file uploads
-
Inspect the update function for validationOpen Template.php and examine the update function for file type validation logic - look for whitelist/blacklist checks on $_FILES or uploaded file extensionsAffected if The update function processes file uploads without proper file type validation or extension checking
-
Check upload directory web accessibilityLocate where uploaded files are stored (check for upload directory paths in the code) and verify if this directory is accessible via HTTPAffected if Uploaded files are stored in a web-accessible directory with PHP execution permissions
-
Test upload functionality accessDetermine if the Template controller update function is accessible to unauthenticated or low-privilege users by checking authentication requirements in the controllerAffected if The file upload endpoint is accessible without proper authentication or authorization controls
You are affected if CLTPHP version is 6.0 or below AND the Template controller's update function processes file uploads without validation AND uploaded files are stored in a web-accessible location with executable permissions.
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 whitelist-based file type validation, verify file content/magic bytes, rename uploaded files to safe names, and store uploads outside the web root or with non-executable permissions.
- Consultation4.0 h
- Implementation8.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30264 — 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-2023-30264 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