CVE-2025-24775
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.9.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 Forms plugin for WordPress has an unrestricted file upload vulnerability allowing attackers to upload malicious PHP files (web shells) directly to the web server. Since no file type validation is performed, attackers can bypass restrictions and execute arbitrary commands with the privileges of the web server user.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the Forms plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for a Forms plugin (such as WPForms, Contact Form 7, or similar). Note the exact plugin name and installed version.Affected if Any version of a WordPress forms plugin is installed and the installed version is below 2.9.1
-
Verify the installed version against affected rangeCompare the installed Forms plugin version to version 2.9.1. In WordPress admin, click on the plugin to view its details and version number.Affected if The installed version is lower than 2.9.1 (e.g., 2.9.0, 2.8.x, or earlier)
-
Inspect uploads directory for unexpected filesNavigate to the /wp-content/uploads/ directory via FTP, file manager, or command line. Look for PHP files, especially with suspicious names or in unexpected subdirectories.Affected if PHP files exist in the uploads directory, particularly files that were not intentionally uploaded through legitimate forms
-
Check for unauthorized form submissionsReview the form entry logs or database tables for form submissions containing suspicious file uploads, especially submissions from unfamiliar IP addresses or with unusual file types.Affected if Form entries contain uploads with .php extensions or other executable file types
-
Examine web server access logs for upload activityReview web server access logs (Apache access.log, Nginx access.log) for POST requests to upload endpoints, looking for requests that upload files with PHP extensions to the uploads directory.Affected if HTTP POST requests to upload handlers contain .php file extensions in the request
You are affected if the WordPress Forms plugin is installed with a version lower than 2.9.1 and the file upload functionality is accessible on your site.
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.9.1 or later which includes proper file type validation. Additionally, configure the web server to prevent script execution in the uploads directory and implement .htaccess rules to block PHP file execution.
Update to version 2.9.1 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Forms by Made I.T.' in the plugin list
- 4. Check if an update is available for the plugin
- 5. If an update is available, update the plugin to the latest version
- 6. Verify the update was successful by checking the plugin version after update
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-24775 — 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-2025-24775 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