dbcve.org
CWE-345Weakness · CWE-345

CVE-2026-9242

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Verification of Data Authenticity in all versions up to and including 6.0.8.6. This is due to the PayPal IPN `callback` handler being registered as a nopriv AJAX action with no authentication or nonce requirement, and critically because the handler updates the payment log database row with attacker-controlled POST data — including `payment_status` and the `custom` field encoding the target `user_id` — before PayPal IPN validation is performed, meaning the database remains poisoned even when validation subsequently fails. This makes it possible for unauthenticated attackers to authenticate as any WordPress user, including administrators, by submitting a forged IPN request that overwrites a payment log entry's `user_id` with that of a target account, then visiting the success return URL with a legitimately obtained security hash to cause the plugin to issue real WordPress authentication cookies for the targeted account.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RegistrationMagic WordPress plugin has an authentication bypass vulnerability in its PayPal IPN callback handler. The AJAX endpoint is registered as nopriv (accessible without authentication) and updates payment log database entries with attacker-controlled POST data—including payment_status and user_id—BEFORE performing PayPal IPN validation. This allows unauthenticated attackers to poison payment log entries by overwriting the user_id to a target account, then visiting the success return URL with a legitimately obtained security hash to obtain valid WordPress authentication cookies for that target user, including administrators.

MitigationUpdate the plugin to version 6.0.8.7 or later which implements proper authentication and performs PayPal IPN validation before updating database records. As an interim measure, consider disabling the PayPal integration or restricting the AJAX endpoint via .htaccess rules if immediate patching is not possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if RegistrationMagic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'RegistrationMagic' or 'RegistrationMagic Premium'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'registrationmagic' or 'registration-magic'.
    Affected if The plugin is present in the WordPress installation.
  2. Determine the installed plugin version
    In WordPress admin plugins list, find the Version column for RegistrationMagic. Alternatively, open /wp-content/plugins/registrationmagic/readme.txt (or similar) and check the version header.
    Affected if The version is lower than 6.0.8.7.
  3. Check if PayPal integration is enabled
    Navigate to RegistrationMagic settings in the WordPress admin panel. Look for PayPal or Payment settings. The vulnerability requires PayPal IPN callback to be configured and active.
    Affected if PayPal IPN integration is enabled and the plugin is handling PayPal payment notifications.
  4. Verify the AJAX endpoint is publicly accessible
    Check the WordPress site for the AJAX handler at /wp-admin/admin-ajax.php?action=rm_paypal_ipn (or similar PayPal IPN action). This endpoint should respond or accept POST requests without authentication.
    Affected if The endpoint is reachable without authentication (nopriv capability).

A user is affected if RegistrationMagic plugin is installed with a version below 6.0.8.7 and PayPal IPN integration is enabled, allowing unauthenticated access to the payment log manipulation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 6.0.8.7 or later which implements proper authentication and performs PayPal IPN validation before updating database records. As an interim measure, consider disabling the PayPal integration or restricting the AJAX endpoint via .htaccess rules if immediate patching is not possible.

Recommended fix Moderate confidence

6.0.8.7 or later (verify current latest version at plugins.trac.wordpress.org)

  1. Check the WordPress plugin repository for RegistrationMagic for the latest available version
  2. If version 6.0.8.7 or later is available, upgrade to that version via WordPress admin > Plugins > Update Now
  3. If no fixed version is available yet, disable the PayPal integration in RegistrationMagic settings as a temporary mitigation
  4. Alternatively, restrict access to the /wp-admin/admin-ajax.php endpoint for unauthenticated users using a WAF or web server configuration
  5. Monitor the plugin's changelog and security advisories for updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9242 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9242 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data