dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1054

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-28
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 plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 6.0.7.4. This is due to missing nonce verification and capability checks on the rm_set_otp AJAX action handler. This makes it possible for unauthenticated attackers to modify arbitrary plugin settings, including reCAPTCHA keys, security settings, and frontend menu titles.

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 versions up to 6.0.7.4 contain a missing authorization vulnerability in the rm_set_otp AJAX action handler. The handler lacks both nonce verification and capability/permission checks, allowing unauthenticated attackers to invoke it and modify arbitrary plugin settings including reCAPTCHA keys, security settings, and frontend menu titles.

MitigationUpdate the RegistrationMagic plugin to version 6.0.7.5 or later which implements proper authorization checks (nonce verification and capability validation) on the affected AJAX endpoint. Until patched, consider disabling the affected AJAX endpoint via firewall rules or monitoring for suspicious rm_set_otp requests.

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. Confirm RegistrationMagic plugin is installed
    Locate the RegistrationMagic plugin in the WordPress installation: check wp-content/plugins/registrationmagic/ directory, or view the installed plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if Plugin files exist in the WordPress installation and the plugin is active
  2. Identify the installed plugin version
    Open the main plugin file (registrationmagic.php) and locate the Version header in the plugin comment block, or view the version number in WordPress admin plugin list
    Affected if Installed version is 6.0.7.4 or lower (any version up to and including 6.0.7.4)
  3. Test if AJAX endpoint accepts unauthenticated requests
    Send a crafted POST request to /wp-admin/admin-ajax.php with parameter action=rm_set_otp (no authentication required), using curl or browser developer tools. Observe if the server responds with a valid AJAX response rather than redirecting to login or returning 403
    Affected if Endpoint responds with 200 OK and returns a non-error response without requiring login credentials
  4. Verify plugin settings integrity
    In WordPress admin, navigate to RegistrationMagic settings panels and check: reCAPTCHA configuration (Keys section), security settings, and frontend menu/label configurations. Look for unexpected values or unauthorized modifications
    Affected if Settings show unauthorized changes, unfamiliar reCAPTCHA keys, or altered values not set by the legitimate administrator

Environment is affected if RegistrationMagic plugin version is 6.0.7.4 or lower AND the rm_set_otp AJAX endpoint responds to unauthenticated requests without requiring login or capability verification.

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 RegistrationMagic plugin to version 6.0.7.5 or later which implements proper authorization checks (nonce verification and capability validation) on the affected AJAX endpoint. Until patched, consider disabling the affected AJAX endpoint via firewall rules or monitoring for suspicious rm_set_otp requests.

Recommended fix High confidence

RegistrationMagic version 6.0.7.5 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the RegistrationMagic plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Verify the update completed successfully
  6. Confirm the plugin is running version 6.0.7.5 or later
Caveat Review plugin settings after upgrade as any custom configurations should be preserved, but verify reCAPTCHA and security settings are intact

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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