dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14080

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Frontend Post Submission Manager Lite plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.2.5. This is due to missing authorization checks on the post update functionality in the fpsml_form_process AJAX action. This makes it possible for unauthenticated attackers to modify arbitrary posts by providing a post_id parameter via the guest posting form, allowing them to change post titles, content, excerpts, and remove post authors.

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 confidence

The Frontend Post Submission Manager Lite WordPress plugin has a missing authorization vulnerability in the fpsml_form_process AJAX action. Unauthenticated attackers can supply a post_id parameter via the guest posting form to modify arbitrary posts, allowing unauthorized changes to post titles, content, excerpts, and author assignments.

MitigationUpdate to plugin version 1.2.6 or later which includes proper authorization checks, or add WordPress capability checks and nonce validation to the fpsml_form_process AJAX action.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Frontend Post Submission Manager Lite' or check the plugin files in /wp-content/plugins/frontend-post-submission-manager-lite/ for version information in the main PHP file header.
    Affected if Plugin is not installed or not present on the system
  2. Identify installed plugin version
    Open the main plugin file (usually frontend-post-submission-manager-lite.php) and locate the 'Version' header in the plugin comment block, or check the plugin metadata via wp-cli: wp plugin list --filter=frontend-post-submission-manager-lite
    Affected if Version is below 1.2.6 (the version that includes the fix)
  3. Confirm AJAX action is exposed
    Check if the fpsml_form_process AJAX action is accessible without authentication by inspecting the plugin code for add_action('wp_ajax_nopriv_fpsml_form_process') or by testing a POST request to /wp-admin/admin-ajax.php with action=fpsml_form_process
    Affected if The AJAX action is registered for unauthenticated access (wp_ajax_nopriv) and responds to requests
  4. Check if post submission form is active
    Look for any published page or post containing the plugin's shortcode (commonly [fpsml_post_form] or similar) that enables public/guest post submissions, or check the plugin settings for enabled post types.
    Affected if A public-facing submission form exists and is accessible to unauthenticated users, allowing them to supply a post_id parameter

A user is affected if the plugin is installed with a version below 1.2.6 AND the fpsml_form_process AJAX action is exposed to unauthenticated users AND a public submission form is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to plugin version 1.2.6 or later which includes proper authorization checks, or add WordPress capability checks and nonce validation to the fpsml_form_process AJAX action.

Recommended fix Moderate confidence

Version 1.2.6 or later (latest stable release)

  1. Update the Frontend Post Submission Manager Lite plugin to the latest available version from the WordPress plugin repository
  2. After updating, verify that the fpsml_form_process AJAX action now properly checks user permissions before allowing post modifications
  3. Confirm that unauthenticated users can no longer modify arbitrary posts via the plugin's submission form
  4. Test that legitimate functionality for authenticated users submitting posts still works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14080 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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