CVE-2024-1353
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, has been found in PHPEMS up to 1.0. Affected by this issue is the function index of the file app/weixin/controller/index.api.php. The manipulation of the argument picurl leads to deserialization. The exploit has been disclosed to the public and may be used. VDB-253226 is the identifier assigned to this vulnerability.
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 confidencePHPEMS up to v1.0 contains a PHP Object Injection vulnerability in app/weixin/controller/index.api.php where the index function deserializes user-supplied data from the picurl parameter without proper validation. An unauthenticated attacker can craft malicious serialized PHP objects to achieve remote code execution if suitable POP chains exist in the application.
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.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.
-
Locate PHPEMS installationSearch the web server document root for the PHPEMS application directory, typically identifying the presence of 'app/weixin/controller/index.api.php' or other PHPEMS-specific file structures.Affected if The application files exist on the server.
-
Determine installed PHPEMS versionCheck for a version file or header within the PHPEMS installation (commonly in a version.php, README, or configuration file). Compare the found version against the affected range: <= 1.0.Affected if The installed version is 1.0 or lower.
-
Inspect the vulnerable fileExamine the file 'app/weixin/controller/index.api.php' and locate the index function. Search for unserialize() calls that process the 'picurl' parameter from user input.Affected if The file contains an unserialize() call on the picurl parameter without prior validation.
-
Verify weixin module accessibilityConfirm that the weixin controller endpoint is accessible via the web server (e.g., accessing the index.api.php endpoint directly or through the application's routing).Affected if The weixin module endpoint is reachable over the network.
The environment is affected if PHPEMS version 1.0 or lower is installed, the vulnerable file app/weixin/controller/index.api.php contains an unserialize() call on the picurl parameter, and the weixin endpoint is web-accessible.
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 dataReplace unsafe unserialize() calls on the picurl parameter with json_decode() or implement strict input validation/whitelisting before any deserialization occurs. If deserialization is required, use a safe deserialization library with class whitelisting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1353 — 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-1353 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