CVE-2019-15524
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 · uneditedCSZ CMS 1.2.3 allows arbitrary file upload, as demonstrated by a .php file to admin/filemanager in the File Management Module, which leads to remote code execution by visiting a photo/upload/2019/ URI.
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 confidenceCSZ CMS 1.2.3 contains an authenticated arbitrary file upload vulnerability in the File Management Module (admin/filemanager). An attacker with admin credentials can upload malicious .php files to the photo/upload/ directory, which are directly executable by the web server, enabling 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= 1.2.3CVSS 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.0/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 CSZ CMS installation and versionLocate the CSZ CMS installation and identify the installed version number from the system configuration, admin dashboard, or version fileAffected if The installed version is exactly 1.2.3
-
Determine if File Management Module is enabledAccess the admin interface and check whether the File Management Module (admin/filemanager) is present and accessibleAffected if The File Management Module is active and accessible to admin users
-
Verify photo/upload directory is web-accessibleCheck the web server document root for the existence of the photo/upload/ directory and confirm it is directly accessible via HTTP/HTTPS without authentication barriersAffected if The photo/upload/ directory exists and is web-accessible
-
Check for execution restrictions on upload directoryInspect the photo/upload/ directory for .htaccess rules or web server configuration that prevent execution of uploaded .php filesAffected if No restrictions exist to prevent execution of uploaded PHP files in the photo/upload/ directory
If running CSZ CMS version 1.2.3 with the File Management Module enabled and the photo/upload/ directory is web-accessible without script execution restrictions, the environment is vulnerable to remote code execution via uploaded PHP files.
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 dataImmediately disable or restrict the file upload functionality in the File Management Module, implement strict allowlist-based file type validation with magic byte checking, store uploads outside the webroot, and add .htaccess rules to prevent execution of uploaded files.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15524 — 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-2019-15524 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