Money Space <= 2.13.9 - Unauthenticated Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 2.14.0
- Affected Plugin
- Money Space
- Affected Version
<= 2.13.9- CVSS
- 8.6High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-13371
At a glance
CVE-2025-13371 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Money Space WordPress plugin, affecting versions <= 2.13.9. It carries a CVSS score of 8.6 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.14.0; sites on affected versions should update now. Disclosed January 2026, reported by Kannika Khongpan.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Money Space <= 2.13.9 carries this weakness at base64_encode(), and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Money Space the fix is 2.14.0: builds <= 2.13.9 are affected, anything from 2.14.0 onward is not.
Remediation
Update to version 2.14.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Money Space 2.14.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C