dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-4105

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-21
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 Splitit plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on several functions in the 'splitIt-flexfields-payment-gateway.php' file in all versions up to, and including, 4.2.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change plugin settings, including changing the environment from sandbox to production and vice versa.

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 Splitit WordPress plugin up to version 4.2.8 lacks proper capability checks on several functions in splitIt-flexfields-payment-gateway.php. This allows any authenticated user with Subscriber-level access or higher to modify critical plugin settings, including toggling between sandbox and production environments, through unprotected AJAX or form handlers.

MitigationUpdate to version 4.2.9 or later which implements proper capability checks. Until then, consider restricting user registration or removing the plugin.

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 Splitit plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Splitit' or check the filesystem at /wp-content/plugins/ for a directory containing 'splitit' or 'splitIt-flexfields-payment-gateway'
    Affected if The Splitit plugin directory exists in the plugins folder
  2. Identify installed version
    Open the main plugin file (splitIt-flexfields-payment-gateway.php) and look for the version header comment, or check the plugin's readme.txt for the 'Stable tag' entry
    Affected if The reported version is 4.2.8 or earlier
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the Splitit plugin shows as 'Active'
    Affected if The plugin is currently activated
  4. Check for subscriber-level users
    Go to WordPress admin > Users and review user accounts. Look for any users with the 'Subscriber' role, or check user_role meta for roles containing 'subscriber'
    Affected if At least one user with Subscriber role or higher exists on the site
  5. Inspect vulnerable file presence
    Check that splitIt-flexfields-payment-gateway.php exists in the plugin directory. This file contains the AJAX handlers and form handlers lacking capability checks
    Affected if The file splitIt-flexfields-payment-gateway.php is present in the plugin directory

If the Splitit plugin version is 4.2.8 or earlier, is active, and any subscriber-level user account exists on the WordPress site, the environment is affected by this 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 version 4.2.9 or later which implements proper capability checks. Until then, consider restricting user registration or removing the plugin.

Recommended fix Moderate confidence

Version greater than 4.2.8 (latest version available in the WordPress plugin repository)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Splitit plugin
  4. Check if the current version is 4.2.8 or below
  5. If vulnerable, update the plugin to the latest available version from the WordPress plugin repository

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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