CVE-2025-15520VulnerabilityPublished 13 Feb 2026

CVE-2025-15520: RegistrationMagic (WordPress plugin) · Information Exposure

Affects RegistrationMagic (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 6.0.7.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.0.7.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade RegistrationMagic (WordPress plugin) to 6.0.7.2.

Affected software

Product	Affected	Fixed in
RegistrationMagic	Affected <6.0.7.2	Fixed in 6.0.7.2

AI-suggested

To mitigate CVE-2025-15520, organizations should immediately update the RegistrationMagic plugin to version 6.0.7.2 or later, where the vulnerability is patched. In addition, administrators should audit user roles and permissions to restrict subscriber-level accounts from accessing sensitive areas of the site unnecessarily. Implementing the principle of least privilege by limiting user registrations or disabling unnecessary accounts can reduce exposure. Monitoring logs for unusual access patterns or attempts to access restricted data can help detect exploitation attempts. Employing Web Application Firewalls (WAFs) with rules tailored to block suspicious requests targeting the plugin endpoints may provide additional protection. Regular security assessments and plugin updates should be part of the WordPress site maintenance routine to prevent similar vulnerabilities. Finally, educating site administrators about the importance of capability checks in plugin development can help avoid such issues in custom or third-party plugins.

Description

The RegistrationMagic WordPress plugin before 6.0.7.2 checks nonces but not capabilities, allowing for the disclosure of some sensitive data to subscribers and above.

Impact

The primary impact of CVE-2025-15520 is unauthorized disclosure of sensitive information to users with subscriber-level access or above. This can lead to leakage of personal data, configuration details, or other sensitive content managed by the RegistrationMagic plugin. While the vulnerability does not allow modification or deletion of data, the exposure of confidential information can aid attackers in crafting targeted phishing campaigns, privilege escalation attempts, or other follow-on attacks. Organizations relying on RegistrationMagic for form management on WordPress sites may face reputational damage, compliance violations (e.g., GDPR), and loss of customer trust if sensitive data is exposed. Since the vulnerability requires authenticated access, the risk is somewhat mitigated by the need for user accounts, but many WordPress sites allow user registrations at subscriber level by default, increasing the attack surface. The absence of known exploits reduces immediate risk, but the medium severity score indicates that timely patching is important to prevent potential abuse.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/996f1c93-4b28-4cec-9d7c-fb66d0addabc/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Feb 2026, 09:07 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats