dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-13371

HIGH · 8.6 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 MoneySpace plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.13.9. This is due to the plugin storing full payment card details (PAN, card holder name, expiry month/year, and CVV) in WordPress post_meta using base64_encode(), and then embedding these values into the publicly accessible mspaylink page's inline JavaScript without any authentication or authorization check. This makes it possible for unauthenticated attackers who know or can guess an order_id to access the mspaylink endpoint and retrieve full credit card numbers and CVV codes directly from the HTML/JS response, constituting a severe PCI-DSS violation.

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 MoneySpace WordPress plugin (versions up to 2.13.9) stores full payment card details (PAN, cardholder name, expiry, CVV) in WordPress post_meta using base64_encode() - a reversible encoding, NOT encryption. These card details are embedded in the publicly accessible mspaylink page's inline JavaScript without any authentication or authorization, allowing unauthenticated attackers who know or guess an order_id to extract complete credit card data directly from the HTML/JS response.

MitigationDisable the mspaylink endpoint immediately, remove all stored card data from post_meta, implement proper AES encryption with secure key management, add authentication/authorization checks, and conduct a PCI-DSS compliance audit. Affected users should be notified of potential card compromise.

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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. Identify MoneySpace plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'MoneySpace' or 'mspay'. Alternatively, check the plugin directory (wp-content/plugins/) for a folder named 'moneyspace' or similar. Check the plugin's main PHP file for the version number, typically in the plugin header comment.
    Affected if MoneySpace plugin is installed and version is 2.13.9 or lower (or if version cannot be determined and plugin is present)
  2. Verify mspaylink endpoint is active
    Visit your site URL with '/mspaylink' or '/mspay/link' path appended (e.g., yourdomain.com/mspaylink). If the page loads without requiring login or authentication, the endpoint is publicly accessible.
    Affected if The mspaylink endpoint loads without any authentication or authorization requirement
  3. Check for stored order post_meta
    Use WordPress database query: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%card%' OR meta_key LIKE '%pan%' OR meta_key LIKE '%cvv%' OR meta_key LIKE '%cardholder%' (adjust prefix 'wp_' if different). Look for meta_value contents that appear to be base64-encoded strings containing payment card data.
    Affected if post_meta contains records with base64-encoded strings that decode to reveal PAN, cardholder name, expiry date, or CVV
  4. Inspect HTML response from mspaylink for exposed card data
    Visit the mspaylink page with a known order_id parameter (e.g., /mspaylink?order_id=123). View page source (Ctrl+U) or inspect the response with browser DevTools (Network tab). Search for strings resembling credit card numbers, base64 patterns, or card-related JavaScript variables.
    Affected if The HTML/JavaScript response contains unmasked or reversibly-encoded credit card numbers, cardholder names, or CVV values

A user is affected if the MoneySpace plugin (version 2.13.9 or lower) is installed, the mspaylink endpoint is publicly accessible, and payment card data exists in post_meta or is exposed in mspaylink page responses.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the mspaylink endpoint immediately, remove all stored card data from post_meta, implement proper AES encryption with secure key management, add authentication/authorization checks, and conduct a PCI-DSS compliance audit. Affected users should be notified of potential card compromise.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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