CVE-2026-2899
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 Fluent Forms Pro Add On Pack plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 6.1.17. This is due to the `deleteFile()` method in the `Uploader` class lacking nonce verification and capability checks. The AJAX action is registered via `addPublicAjaxAction()` which creates both `wp_ajax_` and `wp_ajax_nopriv_` hooks. This makes it possible for unauthenticated attackers to delete arbitrary WordPress media attachments via the `attachment_id` parameter. Note: The researcher described file deletion via the `path` parameter using `sanitize_file_name()`, but the actual code uses `Protector::decrypt()` for path-based deletion which prevents exploitation. The vulnerability is exploitable via the `attachment_id` parameter instead.
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 Fluent Forms Pro Add On Pack plugin for WordPress versions up to 6.1.17 has a missing authorization vulnerability in the Uploader class deleteFile() method. The AJAX action is registered with public hooks (wp_ajax_nopriv_) allowing unauthenticated access, and lacks both nonce verification and capability checks, enabling any visitor to delete arbitrary WordPress media attachments by supplying an attachment_id.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Verify Fluent Forms Pro Add On Pack is installedIn WordPress admin, go to Plugins and look for 'Fluent Forms Pro Add On Pack' or check the plugins directory for the plugin filesAffected if The plugin is not installed or not present in the system
-
Check the plugin versionView the plugin header in its main PHP file or check the installed version in WordPress admin Plugins listAffected if The installed version is 6.1.17 or lower (any version up to and including 6.1.17)
-
Locate the Uploader class deleteFile methodSearch the plugin files for the Uploader class and its deleteFile method - typically in includes or classes directories within the pluginAffected if The deleteFile method exists and is present in the plugin code
-
Check AJAX hook registration for deleteFileSearch the plugin code for the AJAX action registration related to deleteFile - look for wp_ajax_nopriv_ hooks which allow unauthenticated accessAffected if The AJAX action is registered with wp_ajax_nopriv_ hook, allowing any visitor to trigger it without authentication
-
Verify missing authorization checks in deleteFileExamine the deleteFile method code for nonce verification (check_ajax_referer or wp_verify_nonce) and capability checks (current_user_can with delete_post permission)Affected if The deleteFile method lacks both nonce verification and capability checks, allowing unauthenticated deletion of any media attachment
A user is affected if the Fluent Forms Pro Add On Pack plugin is installed with version 6.1.17 or lower and the deleteFile AJAX action is accessible without authentication (registered with wp_ajax_nopriv_ hook).
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 dataAdd nonce verification and capability checks (e.g., current_user_can('delete_post', $attachment_id)) to the deleteFile() method, and register the AJAX action without the nopriv hook or add an auth check.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2899 — 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-2899 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