CVE-2026-1280
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 Frontend File Manager Plugin for WordPress is vulnerable to unauthorized file sharing due to a missing capability check on the 'wpfm_send_file_in_email' AJAX action in all versions up to, and including, 23.5. This makes it possible for unauthenticated attackers to share arbitrary uploaded files via email by supplying a file ID. Since file IDs are sequential integers, attackers can enumerate all uploaded files on the site and exfiltrate sensitive data that was intended to be restricted to administrators only.
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 Frontend File Manager Plugin for WordPress has a missing authorization check on the 'wpfm_send_file_in_email' AJAX action, allowing unauthenticated users to share arbitrary uploaded files via email by providing a file ID. Since file IDs are sequential integers, attackers can enumerate all uploaded files and exfiltrate sensitive data.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Frontend File Manager plugin is installedCheck the WordPress plugins directory or wp-content/plugins folder for a folder named 'frontend-file-manager' or similar. Alternatively, query the wp_options table for option_name='active_plugins' and look for the plugin entry.Affected if The plugin folder or database entry exists on the WordPress site
-
Determine the installed plugin versionCheck the plugin main PHP file header for the 'Version' comment, or query the wp_options table for an option containing 'frontend_file_manager' version information.Affected if The installed version is older than the patched version (compare against the latest version on the WordPress plugin repository)
-
Verify the vulnerable AJAX action is exposedSend a POST request to /wp-admin/admin-ajax.php with action=wpfm_send_file_in_email and a file_id parameter, without including any authentication cookies or nonce.Affected if The request returns a successful response (not a 403 or requires-login error) indicating the AJAX endpoint is accessible to unauthenticated users
-
Confirm file upload functionality is enabledCheck if the plugin has any uploaded files in the wp-content/uploads/fpfm or similar directory, or verify that the plugin's file upload feature is not disabled in its settings.Affected if The plugin has active uploaded files that could be enumerated and shared via the vulnerable AJAX action
The site is affected if the Frontend File Manager plugin is installed, the vulnerable AJAX action responds without authentication, and the plugin has uploaded files accessible for enumeration and exfiltration.
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 a capability check (e.g., current_user_can('manage_options')) to the wpfm_send_file_in_email AJAX handler and update to the latest plugin version.
- 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-2026-1280 — 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-1280 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