CVE-2026-19251

Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin < 2.13.0 - Unauthenticated Unapproved Comment and Private Profile Data Disclosure

2026-08-31 00:00
Alessandro Greco

Strategic Overview

Status
Patched in 2.13.0
Affected Version
< 2.13.0
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-19251
View all Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin vulnerabilities

At a glance

CVE-2026-19251 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Ultimate Member WordPress plugin, affecting versions < 2.13.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.13.0; sites on affected versions should update now. Disclosed August 2026, reported by Alessandro Greco.

Vulnerability Overview

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 2.13.0. This is due to missing approval status filter and profile visibility check in the get_comments() calls inside add_comments() and load_comments(). This makes it possible for unauthenticated attackers to read unapproved comments and activity from private profiles without authentication.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Ultimate Member < 2.13.0 carries this weakness at get_comments(), and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Ultimate Member the fix is 2.13.0: builds < 2.13.0 are affected, anything from 2.13.0 onward is not.

Remediation

Update to version 2.13.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Ultimate Member 2.13.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C