Mw Wp FormWordPress extension · Mw Wp Form Project
CVE-2023-28408
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 · uneditedDirectory traversal vulnerability in MW WP Form versions v4.4.2 and earlier allows a remote unauthenticated attacker to alter the website or cause a denial-of-service (DoS) condition, and obtain sensitive information depending on settings.
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 confidenceDirectory traversal vulnerability in MW WP Form WordPress plugin versions v4.2.2 and earlier allows remote unauthenticated attackers to access files outside the web root via path manipulation, enabling website content alteration, denial-of-service, and potential sensitive information disclosure depending on configuration.
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
Mw Wp FormWordPress extension
<= 4.4.2CVSS 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 MW WP Form plugin versionIn WordPress admin dashboard, go to Plugins > Installed Plugins > MW WP Form and check the version number displayed. Alternatively, inspect the plugin header in wp-content/plugins/mw-wp-form/mw-wp-form.php file for the Version field.Affected if The installed version is 4.4.2 or earlier.
-
Verify plugin is activeCheck if MW WP Form is enabled in the WordPress plugins list. The vulnerability is exploitable when the plugin is active.Affected if The plugin status shows as 'Active'.
-
Check for file upload or attachment featuresReview the plugin settings in WordPress admin under MW WP Form > Settings or any form configurations. Look for file upload fields, attachment handling, or mail settings that specify file paths.Affected if Any form created with MW WP Form has file upload functionality enabled or uses mail attachment configurations.
-
Inspect plugin endpoint accessibilityTest if the plugin's ajax or form submission endpoints are accessible. Common paths include /wp-admin/admin-ajax.php?action=mfw_* or direct plugin PHP files in wp-content/plugins/mw-wp-form/. Attempt a controlled path traversal test (e.g., ../../) to a known file if you have a test environment.Affected if The plugin endpoints respond without authentication or proper path validation.
You are affected if MW WP Form plugin version 4.4.2 or earlier is installed and active with file handling features enabled, as the directory traversal flaw can be exploited via plugin endpoints.
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 dataUpdate MW WP Form to version v4.4.3 or later which contains the security patch; if immediate patching is not feasible, consider deploying a WAF rule or temporarily restricting access to the affected plugin endpoints.
Fix this in Mw Wp Form
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28408 — 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-2023-28408 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