dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-12158

HIGH · 8.8 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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 – User Registration Forms Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.0.9.1. This is due to missing or incorrect nonce validation on the process_request function. This makes it possible for unauthenticated attackers to escalate the privileges of an arbitrary form submitter to administrator by creating a malicious Chronos automation task that is executed via WordPress cron via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 lacks proper nonce validation in its process_request function, allowing unauthenticated attackers to forge requests that create malicious Chronos automation tasks. When executed via WordPress cron, these tasks can escalate any form submitter's privileges to administrator level, achieving full site compromise through social engineering of a site administrator.

MitigationUpdate to the patched version of RegistrationMagic once released. Site administrators should avoid clicking untrusted links and consider disabling the plugin until a patch is available.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify RegistrationMagic plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'RegistrationMagic' or check the plugin files in wp-content/plugins/registrationmagic folder for the main PHP file and its version header
    Affected if The plugin is installed and active
  2. Check installed plugin version
    Read the version number from the plugin header in registrationmagic.php or from the WordPress plugins page, then compare to the affected range (versions up to 6.0.9.1)
    Affected if Installed version is 6.0.9.1 or lower
  3. Confirm Chronos automation feature is active
    In WordPress admin, navigate to RegistrationMagic > Chronos (or similar automation settings) and check if any automation tasks are defined or enabled
    Affected if Chronos automation tasks exist or the feature is enabled
  4. Inspect WordPress cron for suspicious RegistrationMagic tasks
    Run wp cron event list via WP-CLI or check the wp_options table for cron entries containing 'rm_cron' or 'registrationmagic' hooks that create admin users or modify roles
    Affected if Cron jobs exist that create administrator accounts or modify user roles on behalf of the plugin
  5. Audit administrator accounts for unauthorized creations
    List all user accounts with administrator role via Users > All Users or SQL query on wp_users and wp_usermeta, noting creation dates and comparing against expected admin accounts
    Affected if There are administrator accounts created unexpectedly, especially around times when suspicious links may have been clicked

A user is affected if the RegistrationMagic plugin is installed with version 6.0.9.1 or lower AND the Chronos automation feature is enabled or has been used, as this allows the CSRF to create privilege escalation cron tasks.

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 to the patched version of RegistrationMagic once released. Site administrators should avoid clicking untrusted links and consider disabling the plugin until a patch is available.

Recommended fix Moderate confidence

6.0.9.2 or later (latest stable release)

  1. Check the current version of the RegistrationMagic plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 6.0.9.1 or earlier, update to the latest available version of the RegistrationMagic plugin
  4. After updating, verify that nonce validation has been properly implemented in the process_request function by reviewing plugin changelog or release notes
  5. Ensure WordPress cron jobs are properly secured and monitor for any suspicious automated tasks
Caveat Review plugin changelog for any breaking changes between your current version and the new version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12158 — 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-12158 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