Post FormWordPress extension · Themekraft
CVE-2024-1170
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 · uneditedThe Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) plugin for WordPress is vulnerable to unauthorized media file deletion due to a missing capability check on the handle_deleted_media function in all versions up to, and including, 2.8.7. This makes it possible for unauthenticated attackers to delete arbitrary media files.
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 Post Form plugin for WordPress contains a handle_deleted_media function that lacks proper capability checks, allowing unauthenticated attackers to delete arbitrary media files on the WordPress site.
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
Post FormWordPress extension
< 2.8.8CVSS 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
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
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 plugin installationNavigate to WordPress admin > Plugins and check if 'Themekraft Post Form' or 'Post Form' plugin is installed and activeAffected if The plugin is installed and active
-
Identify installed versionIn Plugins list, locate the Themekraft Post Form plugin and note the version number displayed beneath the plugin nameAffected if Version is less than 2.8.8 (or version cannot be determined but plugin is present)
-
Verify vulnerability exposureCheck if the WordPress site has any publicly accessible AJAX endpoints or admin-ajax.php routes that may invoke the handle_deleted_media function without authenticationAffected if The site exposes WordPress AJAX functionality that could trigger the vulnerable function without authentication
If the Themekraft Post Form plugin versions below 2.8.8 is installed and active on the WordPress site, the environment is affected by this vulnerability.
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 · scoped2.8.8
Update the plugin to version 2.8.8 or later which contains the patched capability check. If an update is unavailable, disable the plugin or implement a temporary firewall rule to block malicious deletion requests.
2.8.8
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the 'Post Form' plugin (also known as Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions)
- Click 'Update now' if an update is available, or manually upload version 2.8.8 or later
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Post Form
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1170 — 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-1170 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