CVE-2024-46441
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 · uneditedAn arbitrary file upload vulnerability in YPay 1.2.0 allows attackers to execute arbitrary code via a ZIP archive to themePutFile in app/common/util/Upload.php (called from app/admin/controller/ypay/Home.php). The file extension of an uncompressed file is not checked.
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 confidenceYPay 1.2.0 contains an arbitrary file upload vulnerability in the themePutFile function (app/common/util/Upload.php) where uploading a malicious ZIP archive allows attackers to upload files with executable extensions (e.g., .php) without extension validation after decompression. This enables remote code execution on the affected 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 YPay installation and versionLocate the YPay application installation directory and check for version files or headers (e.g., version.php, README, or admin dashboard about page) to confirm the installed version is 1.2.0Affected if The installed version is 1.2.0 exactly, or falls within the range including 1.2.0 and prior versions that lack the patch
-
Verify vulnerable file existsCheck if the file app/common/util/Upload.php exists in the YPay installation directoryAffected if The file app/common/util/Upload.php is present, indicating the vulnerable component is in place
-
Inspect themePutFile functionOpen app/common/util/Upload.php and locate the themePutFile function to verify it performs ZIP decompression without extension validation on extracted filesAffected if The themePutFile function exists and performs ZIP extraction without validating file extensions of uncompressed files
-
Confirm upload feature accessibilityDetermine if the theme upload or file upload endpoint is accessible to unauthenticated or low-privilege users (check routing/permissions for themePutFile)Affected if The upload functionality is exposed without strict access controls, allowing external attackers to invoke the vulnerable function
-
Check for extension validation logicSearch the Upload.php file for extension filtering code (e.g., checks for .php, .phtml, .exe, or a whitelist) occurring after ZIP decompressionAffected if No extension validation exists after decompression, or only minimal/missing checks allow executable extensions to pass through
-
Audit upload directory configurationInspect the web server configuration and application settings to identify where uploaded files are stored (typically a themes or uploads folder accessible via web)Affected if Extracted files are stored in a web-accessible directory, enabling the uploaded .php files to be executed via HTTP requests
A system is affected if it runs YPay version 1.2.0 (or prior versions) with the vulnerable app/common/util/Upload.php file present, the themePutFile function accessible, and no extension validation performed on files extracted from uploaded ZIP archives.
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 extension whitelist validation for all uncompressed files extracted from ZIP archives, rejecting executable extensions like .php, .phtml, and .exe before saving any files to disk.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46441 — 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-46441 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