CVE-2025-15520

RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login <= 6.0.7.1 - Authenticated (Subscriber+) Information Exposure

2026-01-23 00:00
Maktoum (bRpsd)

Strategic Overview

Status
Patched in 6.0.7.2
Affected Version
<= 6.0.7.1
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2025-15520
View all RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login vulnerabilities

At a glance

CVE-2025-15520 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 6.0.7.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.0.7.2; sites on affected versions should update now. Disclosed January 2026, reported by Maktoum (bRpsd).

Vulnerability Overview

The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.0.7.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive user or configuration data.

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.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in RegistrationMagic <= 6.0.7.1 takes an account at Subscriber level or above. 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 RegistrationMagic the fix is 6.0.7.2: builds <= 6.0.7.1 are affected, anything from 6.0.7.2 onward is not.

Remediation

Update to version 6.0.7.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: RegistrationMagic 6.0.7.2 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C