CVE-2024-0864
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 · uneditedEnabling Simple Ajax Uploader plugin included in Laragon open-source software allows for a remote code execution (RCE) attack via an improper input validation in a file_upload.php file which serves as an example. By default, Laragon is not vulnerable until a user decides to use the aforementioned plugin.
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 confidenceA critical RCE vulnerability exists in the Simple Ajax Uploader plugin's file_upload.php example file in Laragon, caused by improper input validation that allows attackers to upload and execute malicious files remotely.
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< 7.0.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 Laragon installationLocate the Laragon installation directory. Check for the presence of Laragon software and its version number, typically found in the Laragon control panel or in the installation folder.Affected if Laragon version is below 7.0.0 or version cannot be determined
-
Locate Simple Ajax Uploader pluginSearch the Laragon installation for the Simple Ajax Uploader plugin directory. Look for folders named 'simple-ajax-uploader' or similar in the Laragon www root or in the plugins directory.Affected if The Simple Ajax Uploader plugin directory exists in the Laragon environment
-
Find the vulnerable example fileWithin the Simple Ajax Uploader directory, locate the file_upload.php example file. This file is typically found in the 'example' or 'examples' subdirectory of the plugin.Affected if The file_upload.php example file exists in the Simple Ajax Uploader plugin directory
-
Verify upload functionality exposureDetermine if the file_upload.php is accessible over the web. Check the web server configuration and the file permissions to see if the file can be accessed via HTTP/HTTPS requests.Affected if The file_upload.php example file is web-accessible and accepts file uploads without proper validation
The environment is affected if Laragon version is below 7.0.0 and the Simple Ajax Uploader plugin with its file_upload.php example file is present and 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.
dbcve · scoped7.0.0
Users should either remove/disable the Simple Ajax Uploader plugin and its example file_upload.php, or implement proper file type validation, filename sanitization, and upload directory restrictions to prevent arbitrary file execution.
Laragon 7.0.0
- Backup your current Laragon installation and any projects data
- Download Laragon version 7.0.0 from the official laragon.org website
- If you were using the Simple Ajax Uploader plugin, ensure the vulnerable file_upload.php example file is not accessible or remove it
- Install or upgrade to Laragon 7.0.0
- After upgrade, verify that any file upload functionality follows secure coding practices and input validation
- If you do not need the Simple Ajax Uploader plugin, keep it disabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0864 — 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-0864 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