dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-12073

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 ProfileGrid – User Profiles, Groups and Communities plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 5.9.9.5. This is due to the plugin not validating a `user_login` on registration forms that don't contain this parameter, and not properly handling the error messages. This makes it possible for unauthenticated attackers to change email address of user account with ID=1 (usually an administrator), and leverage that to reset the user's password and gain access to their 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 ProfileGrid WordPress plugin fails to validate the user_login parameter on registration forms lacking this field and improperly handles error messages. This allows unauthenticated attackers to modify the email address of the first user account (ID=1, typically admin) and exploit the password reset function to gain full administrative access.

MitigationUpdate the ProfileGrid plugin to a version beyond 5.9.9.5 immediately. Review user account ID=1 for unauthorized changes and consider resetting its password as a precaution.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm ProfileGrid plugin installation and version
    Navigate to WordPress admin > Plugins, locate ProfileGrid, and note the installed version number. Alternatively, inspect the main plugin file header in wp-content/plugins/profilegrid/ for the 'Version' field.
    Affected if The installed version is earlier than 5.9.9.6 (e.g., 5.9.9.5, 5.9.8.x, etc.)
  2. Verify user registration is enabled
    Go to WordPress Settings > General and confirm 'Membership: Anyone can register' is checked, or inspect the site registration URL to confirm registration forms are active.
    Affected if User registration is enabled on the site
  3. Check user ID=1 email address
    Query the wp_users table (via phpMyAdmin or WP-CLI 'wp user get 1') and examine the user_email field for user ID=1 (the first admin account).
    Affected if The email address for user ID=1 has been changed from the original administrator email to an unfamiliar address, or shows signs of recent modification
  4. Inspect registration logs for suspicious activity
    Review WordPress activity logs, ProfileGrid logs, or server access logs for registration requests that may have targeted user ID=1 or attempted to modify the admin email.
    Affected if Unusual or bulk registration attempts are logged, especially those with error messages related to user_login or email fields
  5. Check for password reset anomalies
    Review password reset emails sent from the site (check mail logs or WordPress security plugins) for unexpected password reset requests for the admin account.
    Affected if Password reset emails for the administrator account were sent to unfamiliar email addresses

The environment is affected if ProfileGrid plugin version is below 5.9.9.6 AND user registration is enabled AND user ID=1 email has been modified or password reset activity is detected.

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 ProfileGrid plugin to a version beyond 5.9.9.5 immediately. Review user account ID=1 for unauthorized changes and consider resetting its password as a precaution.

Recommended fix Moderate confidence

ProfileGrid version 5.9.9.6 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate ProfileGrid – User Profiles, Groups and Communities
  4. If an update is available, click 'Update Now'
  5. After updating, verify the version number matches or exceeds the patched release
  6. Consider changing the password for user ID=1 (primary administrator) as a precautionary measure

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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