CVE-2024-51791
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 Made I.T. Forms forms-by-made-it allows Upload a Web Shell to a Web Server.This issue affects Forms: from n/a through <= 2.8.0.
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 confidenceThe Made I.T. Forms plugin allows unrestricted file uploads without proper validation of file types or content. Attackers can upload malicious PHP scripts (web shells) that can then be executed on the server to achieve remote code execution and full system 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.
-
Confirm Made I.T. Forms plugin is installedAccess your WordPress admin panel, navigate to Plugins, and verify the Made I.T. Forms plugin appears in the installed plugins listAffected if The plugin is active and installed in the environment
-
Check the installed version numberIn the WordPress plugins list, click on the plugin details or view the plugin files to locate the version number in the main plugin file header (usually forms.php or similar)Affected if The installed version is lower than 2.8.1 (the fixed release)
-
Verify if file upload forms are enabledNavigate to the plugin settings in the WordPress admin panel and check whether any form builder or upload field functionality is activated or publishedAffected if File upload forms are active and accessible to users
-
Inspect upload directory configurationCheck the wp-content/uploads directory and any custom upload paths configured in the plugin settings to see if file type restrictions are properly enforcedAffected if The upload directory allows PHP files or lacks proper file type validation controls
You are affected if the installed version is below 2.8.1 and the file upload feature is enabled or accessible to non-administrator users
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 · scopedUpgrade to version 2.8.1 or later immediately. Until patched, disable the file upload functionality or restrict all access to trusted administrators only.
2.8.1 or later
- 1. Navigate to the WordPress admin dashboard for the affected installation
- 2. Go to Plugins > Installed Plugins
- 3. Locate 'Forms by Made I.T.' in the plugin list
- 4. Check if an update to version 2.8.1 or higher is available
- 5. If an update is available, click 'Update Now' to install the patched version
- 6. After updating, verify the plugin is running version 2.8.1 or higher
- 7. Test file upload functionality to ensure the patch does not break legitimate uploads
- 8. If no update is available through WordPress, manually download version 2.8.1 or higher from the official WordPress plugin repository and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51791 — 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-51791 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