dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-0632

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Fluent Forms Pro Add On Pack plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.1.12 via the 'saveDataSource' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 Fluent Forms Pro Add On Pack plugin for WordPress contains a Server-Side Request Forgery (SSRF) vulnerability in the saveDataSource function affecting all versions up to 6.1.12. Authenticated attackers with Subscriber-level access or higher can exploit this to make arbitrary web requests from the server, potentially reaching internal services and exfiltrating sensitive information.

MitigationUpdate to the latest version of Fluent Forms Pro Add On Pack when available. Until then, restrict access to the saveDataSource functionality to administrative users only or disable the affected feature.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Confirm Fluent Forms Pro Add On Pack is installed
    Navigate to WordPress admin > Plugins and look for 'Fluent Forms Pro Add On Pack' in the installed plugins list, or inspect the plugin directory at /wp-content/plugins/ for a folder containing 'fluentform' and addon-related files
    Affected if The plugin is present on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view its details and note the version number, or open the main plugin PHP file and check the 'Version' header in the plugin comment block
    Affected if The version is 6.1.12 or any earlier version (the flaw affects all versions up to 6.1.12)
  3. Verify authenticated access exists
    Check WordPress user roles by going to Users > All Users in the admin panel, or query the wp_usermeta table for users with roles of 'subscriber' or higher (roles include Subscriber, Contributor, Author, Editor, Administrator)
    Affected if There is at least one user account with Subscriber-level access or higher, regardless of whether that user is trusted
  4. Confirm the saveDataSource functionality is accessible
    Check if the Fluent Forms addon features are enabled by reviewing the plugin settings in Forms > Add-Ons, or attempt to access the saveDataSource function via the WP REST API endpoint /wp-json/fluentform/addons/save-data-source (if the endpoint exists and is not explicitly restricted)
    Affected if The addon functionality is active and accessible to authenticated users with Subscriber-level permissions

A site is affected if the Fluent Forms Pro Add On Pack plugin (version 6.1.12 or earlier) is installed with the saveDataSource feature enabled and at least one authenticated user with Subscriber-level access exists on the site.

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 the latest version of Fluent Forms Pro Add On Pack when available. Until then, restrict access to the saveDataSource functionality to administrative users only or disable the affected feature.

Recommended fix Moderate confidence

Upgrade to a version of Fluent Forms Pro Add On Pack newer than 6.1.12 (check fluentforms.com or WordPress plugin repository for the latest release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Fluent Forms Pro Add On Pack plugin
  4. Check the current installed version (should be 6.1.12 or below)
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from the official Fluent Forms website or WordPress plugin repository
  7. After updating, verify the plugin version is above 6.1.12
  8. Confirm the vulnerability is resolved by testing that the saveDataSource function no longer accepts arbitrary URLs from low-privilege users
Caveat Minor - review release notes for any changes to DataSource functionality

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0632 — 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-2026-0632 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