dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-5076

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-02
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

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 ARMember Premium plugin for WordPress is vulnerable to an insecure password reset mechanism in all versions up to, and including, 7.3.1. The plugin stores a plaintext copy of the password reset key in the `arm_reset_password_key` user meta field when a user requests a password reset. This is in addition to the hashed key that WordPress core stores securely in `wp_users.user_activation_key`. The plaintext key stored in `wp_usermeta` can be used with the plugin's custom `armrp` reset action to set a new password for any user. Combined with another vulnerability such as SQL Injection (CVE-2026-5073, CVE-2026-5074), this makes it possible for unauthenticated attackers to extract the plaintext reset key and take over any user account, including administrators.

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 ARMember Premium WordPress plugin (versions up to 7.3.1) stores plaintext password reset keys in the `arm_reset_password_key` user meta field alongside the secure hashed key that WordPress core maintains. The plugin's custom `armrp` reset action accepts this plaintext key to set new passwords. When chained with SQL injection vulnerabilities (CVE-2026-5073, CVE-2026-5074), unauthenticated attackers can extract these plaintext keys and reset any user account password, including administrators.

MitigationUpdate ARMember Premium to the latest version once available, or remove the plugin if not essential. Implement Web Application Firewall (WAF) rules to block the vulnerable `armrp` action until a patch is applied.

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. Verify ARMember Premium plugin is installed
    Check your WordPress plugins directory or admin panel for ARMember Premium and note the installed version number
    Affected if The installed version is 7.3.1 or lower (any version up to and including 7.3.1)
  2. Inspect the arm_reset_password_key user meta field
    Query your WordPress database (e.g., SELECT * FROM wp_usermeta WHERE meta_key = 'arm_reset_password_key') to see if this meta field exists and contains values
    Affected if The meta field exists and contains plaintext values (any readable key string rather than a hashed value)
  3. Check for recent password reset key entries
    Examine the arm_reset_password_key values to determine if they contain plaintext reset tokens (look for random-looking alphanumeric strings stored directly)
    Affected if Plaintext reset keys are present in the database for any user accounts
  4. Verify armrp custom reset action is accessible
    Check if the WordPress site responds to requests with the 'armrp' action parameter (e.g., ?action=armrp) - this indicates the vulnerable custom reset mechanism is active
    Affected if The custom armrp reset endpoint is accessible and functional on the site

A user is affected if ARMember Premium version 7.3.1 or lower is installed AND the arm_reset_password_key meta field exists with plaintext values in the database, indicating the vulnerable reset key storage is in use.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ARMember Premium to the latest version once available, or remove the plugin if not essential. Implement Web Application Firewall (WAF) rules to block the vulnerable `armrp` action until a patch is applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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