dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31533

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-31
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
Missing Authorization vulnerability in Salesmate.io Salesmate Add-On for Gravity Forms gf-salesmate-add-on allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Salesmate Add-On for Gravity Forms: from n/a through <= 2.0.3.

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 · moderate confidence

This is a missing authorization vulnerability in the Salesmate Add-On for Gravity Forms WordPress plugin. The plugin fails to properly enforce Access Control Lists (ACLs), allowing users to access functionality they should not have permission to access. This could enable authenticated users with lower privileges to perform actions reserved for higher-privilege users.

MitigationUpdate to the latest version of the Salesmate Add-On for Gravity Forms when available. In the interim, restrict access to the plugin by limiting user capabilities and monitoring for unauthorized access attempts.

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
None
Availability
Low

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

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

  1. Verify Salesmate Add-On for Gravity Forms is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder containing 'salesmate' and 'gravity-forms', or look for 'Salesmate' in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is not found in the plugins directory or not listed in WordPress admin
  2. Identify the installed plugin version
    Open the main plugin file (usually named like salesmate-gravity-forms.php or similar in the plugin folder) and look for a version comment or check the plugin header in WordPress admin under Plugins > Installed Plugins > Plugin Details
    Affected if Unable to determine the version or version is unknown/older
  3. Confirm user role and capability configuration
    Navigate to WordPress admin > Users > and review the roles assigned to test users. Check if lower-privilege users (like Subscriber or Contributor) have roles that might accidentally include higher capabilities
    Affected if Lower-privilege users have been assigned capabilities beyond their intended role level
  4. Test ACL enforcement on plugin features
    Log in as a low-privilege user (Subscriber or Contributor) and attempt to access Salesmate-related features in Gravity Forms (Forms > Salesmate Add-On settings). Observe whether access is denied or allowed
    Affected if Low-privilege users can access or modify settings intended only for Administrators

If the Salesmate Add-On for Gravity Forms plugin is installed and low-privilege authenticated users can access admin-level features or settings, the environment is likely affected by this missing authorization vulnerability.

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 the Salesmate Add-On for Gravity Forms when available. In the interim, restrict access to the plugin by limiting user capabilities and monitoring for unauthorized access attempts.

Recommended fix Low confidence

Upgrade to the latest version of Salesmate Add-On for Gravity Forms available from the official WordPress plugin repository or Salesmate.io

  1. Identify the current version of the Salesmate Add-On for Gravity Forms plugin installed on your WordPress site
  2. Log in to your WordPress admin dashboard and navigate to Plugins > Installed Plugins
  3. Locate the Salesmate Add-On for Gravity Forms plugin
  4. Update the plugin to the latest available version from the WordPress plugin repository or vendor
  5. Verify the update was successful by checking the installed version number
  6. Test the plugin functionality to ensure it works correctly after the update
Caveat Review plugin settings and test forms after upgrading to ensure compatibility with your existing Gravity Forms setup

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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