dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49870

HIGH · 7.5 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Cozmoslabs Paid Member Subscriptions paid-member-subscriptions allows SQL Injection.This issue affects Paid Member Subscriptions: from n/a through <= 2.15.1.

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

SQL injection vulnerability in the Cozmoslabs Paid Member Subscriptions WordPress plugin allows attackers to inject malicious SQL commands via unsanitized user input in affected parameters. The vulnerability exists in versions up to and including 2.15.1.

MitigationUpdate the Paid Member Subscriptions plugin to version 2.15.2 or later. If immediate patching is not possible, consider disabling the plugin or implementing web application firewall rules to block SQL injection 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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/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. Check Paid Member Subscriptions plugin version in WordPress admin
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Paid Member Subscriptions' by Cozmoslabs, and read the version number displayed below the plugin name
    Affected if The version listed is 2.15.1 or lower
  2. Check plugin version via filesystem
    Access the WordPress installation via FTP or file manager, navigate to wp-content/plugins/paid-member-subscriptions, open the main plugin PHP file (usually paid-member-subscriptions.php) and locate the version constant in the file header
    Affected if The version constant shows 2.15.1 or lower
  3. Check for custom code using plugin shortcodes or functions
    Search WordPress theme files (functions.php) and custom plugin files for usage of plugin shortcodes like [pms-register], [pms-login], or direct function calls to pms_* functions that handle user input
    Affected if Custom code passes user-supplied input directly to plugin functions without sanitization
  4. Review web server logs for SQL injection attempts
    Examine Apache/nginx access logs for unusual SQL keywords (UNION, SELECT, INSERT, DROP) in query parameters that target pages using the Paid Member Subscriptions plugin
    Affected if Malicious SQL patterns are found in request logs targeting plugin endpoints

You are affected if the installed Paid Member Subscriptions plugin version is 2.15.1 or lower, or if custom code passes unsanitized input to plugin functions handling user data.

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 the Paid Member Subscriptions plugin to version 2.15.2 or later. If immediate patching is not possible, consider disabling the plugin or implementing web application firewall rules to block SQL injection attempts.

Recommended fix Moderate confidence

Latest version higher than 2.15.1 (check wordpress.org for current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Paid Member Subscriptions' plugin
  4. Check if an update is available (version higher than 2.15.1)
  5. If update available, click 'Update Now' to install the latest version
  6. If no update shown, manually download the latest version from wordpress.org or the vendor and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version number in the plugins list

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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