LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32497: WordPress User Verification plugin <= 2.0.45 - Email Verification Bypass vulnerability

Weak Authentication vulnerability in PickPlugins User Verification user-verification allows Authentication Abuse.This issue affects User Verification: from n/a through <= 2.0.45.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32497 affects the PickPlugins User Verification WordPress plugin through version 2.0.45. The issue may let someone bypass email verification, weakening account signup controls. Business impact is mainly unauthorized or improperly verified accounts, not full site takeover based on the provided CVSS data.

Executive priority

Treat as a moderate-priority website identity-control issue. Prioritize sites where verified user identity protects revenue, community trust, restricted content, or fraud controls. Escalate if the plugin is used on high-registration or customer-facing sites.

Technical view

The CVE describes a weak authentication issue, classified as CWE-1390, in user-verification. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

WordPress sites using PickPlugins User Verification plugin versions up to and including 2.0.45 are the likely exposure. Sites relying on email verification to gate registration, membership, comments, purchases, or access should prioritize review.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. The scoring indicates exploitation could be remote and unauthenticated, but the documented impact is limited to integrity of the verification process.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference in the source bundle. No exploit details, active exploitation claim, or specific patched version is provided here. Validate against vendor advisories before concluding final remediation.

Mitigation direction

  • Identify all WordPress sites using the User Verification plugin.
  • Check whether installed versions are 2.0.45 or earlier.
  • Review vendor, WordPress plugin, and Patchstack guidance for a fixed version or workaround.
  • Temporarily strengthen manual approval or secondary verification for new accounts if business-critical.
  • Monitor new user registrations for suspicious or unverified account activation.

Validation and detection

  • Inventory WordPress plugins across production, staging, and managed hosting environments.
  • Confirm the installed user-verification plugin version from trusted administrative records.
  • Review recent registration logs for accounts bypassing expected email verification.
  • Verify current registration workflows still enforce intended verification controls.
  • Document remediation status for every affected WordPress instance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1390: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32497 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-32497Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PickPluginsUser Verificationuser-verification, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1390 · source CWE mapping

Weak Authentication

Weak Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.