CVE-2026-14487
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 Simple Coherent Form plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the removeUploadDir function in all versions up to, and including, 2.4.13. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The scf_get_id_upload endpoint freely issues a valid scf_upload_file_removal nonce to any unauthenticated visitor, and the removal endpoint's secondary hash check is forgeable offline because it relies on a hardcoded salt embedded in the plugin source, meaning neither control presents a real authorization boundary.
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 Simple Coherent Form WordPress plugin (versions up to 2.4.13) has an unauthenticated arbitrary file deletion vulnerability in the removeUploadDir function. Attackers can delete any file on the server because the scf_get_id_upload endpoint issues valid nonces to unauthenticated visitors, and the removal endpoint's secondary hash check relies on a hardcoded salt embedded in the source code rather than proper authorization. Deleting wp-config.php enables trivial RCE.
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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 WordPress installationLook for wp-config.php in the web root directory, or check for wp-content/plugins folderAffected if WordPress is not present then this CVE does not apply
-
Check if Simple Coherent Form plugin is installedLook for the plugin folder at wp-content/plugins/simple-coherent-form or check the WordPress plugins admin panelAffected if Plugin folder or entry not found, then this CVE does not apply
-
Verify installed plugin versionRead the main plugin file header (e.g., simple-coherent-form.php) and locate the 'Version' field, or query the wp_options table for the active_plugins entryAffected if Version is 2.4.13 or lower, or version field cannot be determined (indicating older unversioned release)
-
Inspect for vulnerable endpoint exposureCheck if the file containing scf_get_id_upload function exists in the plugin directory, typically in includes/ or similar pathAffected if The removeUploadDir function and scf_get_id_upload endpoint code is present in the plugin files
-
Confirm hardcoded salt presenceSearch plugin source code for hardcoded salt strings (look for static salt values in hash validation logic within the vulnerable endpoint handler)Affected if Hardcoded salt used in hash validation is found in the plugin code
User is affected if they have WordPress with Simple Coherent Form plugin version 2.4.13 or lower installed and the vulnerable scf_get_id_upload endpoint code is present.
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 the Simple Coherent Form plugin to a version beyond 2.4.13 immediately. If an update is unavailable, disable the plugin or implement web server-level access controls to block the vulnerable endpoints until a patch is released.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14487 — 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-2026-14487 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