Is this vulnerability remotely exploitable?

Yes. Any remote, unauthenticated user who can reach the affected WordPress site and guess or enumerate valid order_id values can attempt to access the mspaylink endpoint and retrieve embedded payment card data.

Does an attacker need authenticated access or a legitimate account?

No. The described behavior does not enforce authentication or authorization on the mspaylink endpoint. Knowledge or guessing of a valid order_id is sufficient to access the exposed information.

What is the safest general fix pattern for this type of issue?

The safest approach is to stop collecting and storing full cardholder data within the application and delegate payment processing to a PCI-compliant provider using tokenization. Any remaining payment-related endpoints should avoid rendering raw card data to the client and must enforce strong, explicit access controls.

Severity:

HIGH RISK

(8.6)

Sensitive Information Exposure (CWE-200) in MoneySpace WordPress Payment Plugin

CVE-2025-13371

Published:

Jan 7, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-306

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

Account Takeover / Loss of Account Control

February 17, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Remote Code Execution on the Server Host

February 17, 2026

Vulnerability Type

Category:

Sensitive Information Exposure

CWE:

CWE-200

Impact:

Exposure of Full Payment Card Data (PAN + CVV)

Severity:

HIGH RISK

(8.6)

CVSS Version:

3.1

Vulnerability Type

Category:

Sensitive Information Exposure

CWE:

CWE-200

Impact:

Exposure of Full Payment Card Data (PAN + CVV)

Severity:

HIGH RISK

(8.6)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Sensitive Information Exposure (CWE-200) in MoneySpace WordPress Payment Plugin

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare