CVE-2024-49314
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in jiangqie JiangQie Free Mini Program jiangqie-free-mini-program allows Upload a Web Shell to a Web Server.This issue affects JiangQie Free Mini Program: from n/a through <= 2.5.2.
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 confidenceUnrestricted file upload vulnerability in JiangQie Free Mini Program (WordPress plugin) allows attackers to upload malicious PHP files (web shells) to the web server. This enables complete remote code execution and full server compromise.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 if JiangQie Free Mini Program plugin is installedCheck WordPress plugins directory or wp-content/plugins folder for 'jiangqie-free-mini-program' or 'jxq' directory. In WordPress admin, go to Plugins > Installed Plugins and look for JiangQie Free Mini Program.Affected if Plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, click on the plugin to view details and note the version number. Alternatively, check the main plugin PHP file (e.g., jiangqie-free-mini-program.php) for the 'Version' header in the plugin comment block.Affected if Version is any version that has not been patched (compare against release notes or security advisories for the fixed version)
-
Verify if file upload functionality is accessibleCheck if the plugin's upload endpoint is exposed. Common paths include /wp-json/jxq/v1/upload or similar REST API endpoints. Use a web scanner or check WordPress logs for requests to plugin upload handlers.Affected if Upload endpoint responds without authentication or with low-privilege user authentication
-
Inspect upload directory configurationCheck plugin settings or code for upload directory path. Verify if uploaded files are stored within the wp-content/uploads directory (web-accessible) rather than outside the web root.Affected if Uploads are stored in web-accessible directories with script execution enabled
-
Check for existing malicious PHP filesSearch wp-content/uploads and subdirectories for .php files. Use command: find wp-content/uploads -name '*.php'. Also check for recently created files with unusual names.Affected if Unexpected PHP files exist in upload directories, especially with obfuscated code or shell-like names
A user is affected if JiangQie Free Mini Program plugin is installed with an unpatched version AND the upload functionality is accessible to attackers, allowing PHP files to be uploaded to web-accessible directories.
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 dataUpgrade to a patched version of JiangQie Free Mini Program. If no patch available, implement strict server-side file type/content validation, rename uploaded files, store uploads outside web root, and disable script execution in upload directories.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49314 — 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-49314 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