CVE-2026-77794 RegistrationMagic CVE debrief

Who should care

Defenders responsible for WordPress installations using the RegistrationMagic plugin should assess exposure and prioritize verification of the plugin version and registration form settings to prevent exploitation.

Why it matters

Defenders should care about CVE-2026-77794 because it allows unauthenticated users to register without paying and obtain an activated account holding the role the form grants, potentially leading to unauthorized account registrations and exploitation. WordPress administrators and security teams should assess exposure, verify plugin versions, and adjust registration form settings to prevent exploitation.

• Potential unauthorized account registrations
• Possible exploitation by unauthenticated users
• Need for verification of plugin version and registration form settings
• Potential impact on user role assignments

Technical summary

The RegistrationMagic WordPress plugin before 6.0.9.9 does not validate a client-supplied quantity multiplier when calculating the total price of a paid registration, allowing unauthenticated users to register without paying and obtain an activated account holding the role the form grants. This vulnerability has a CVSS score of 5.3 and is classified as MEDIUM severity. It affects WordPress installations using the RegistrationMagic plugin, and defenders should prioritize verifying the plugin version and ensuring it is updated to 6.0.9.9 or later to prevent unauthorized account registrations. The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score.

Defensive priority

Defenders should prioritize verifying the version of the RegistrationMagic WordPress plugin and ensuring it is updated to 6.0.9.9 or later to prevent unauthorized account registrations.

Recommended defensive actions

• Verify the version of the RegistrationMagic WordPress plugin and update to 6.0.9.9 or later
• Monitor for unauthorized account registrations
• Review and adjust registration form settings to prevent exploitation
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, additional information on affected versions and remediation steps may require further verification from the vendor or other sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.