Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2025-13371

CVE-2025-13371 - Money Space Plugin

CVE-2025-13371

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.

CVE-2025-13371

HIGH CVSS 8.6 Published 2026-01-07 Updated 2026-01-08
AI Risk Critical (100/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P1 Immediate
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Affected Components 2
Reference Links 5
AI Risk Engine Critical (100/100)
Exploitability Very High
Active Exploitation Likely
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2026-01-07 CVE published and first recorded in the threat feed.
  2. 2026-01-08 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 12 days ago

AI enriched 12 days ago (2026-04-09 08:09 UTC)

Technical Summary

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…

Potential Impact

Severity is HIGH (CVSS 8.6). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Very High based on published exploit references, remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: published exploit references, remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Money Space PLUGIN · money-space Affected range not specified Fixed version not specified
Moneyspace PLUGIN · moneyspace Affected range not specified Fixed version not specified

References

Scroll to top