dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10648

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-15
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 YourMembership Single Sign On – YM SSO Login plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'moym_display_test_attributes' function in all versions up to, and including, 1.1.7. This makes it possible for unauthenticated attackers to read the profile data of the latest SSO login.

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 YourMembership SSO Login WordPress plugin fails to enforce authorization on the moym_display_test_attributes function, allowing unauthenticated users to access sensitive profile data from the most recent SSO login. This is a classic Broken Access Control vulnerability where a sensitive function lacks capability verification.

MitigationUpdate the plugin to version 1.1.8 or later which includes proper capability checks. Until then, consider disabling the plugin or restricting server-level access to prevent unauthenticated 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify the plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'YourMembership SSO Login' or check the wp-content/plugins/ directory for a folder containing 'yourmembership' in the name
    Affected if The plugin appears in the list or directory exists on the server
  2. Check the installed version number
    In WordPress admin, find the plugin in the Installed Plugins list and look under the plugin name for the version number, or open the main plugin PHP file and check the plugin header comment for 'Version: x.x.x'
    Affected if The version number displayed is lower than 1.1.8 or no version is displayed (older than fixed release)
  3. Inspect the vulnerable function file
    Locate the main plugin PHP file (often named yourmembership-sso-login.php or similar) and search for the function named 'moym_display_test_attributes'. Check if the function contains any capability checks like 'current_user_can' before executing
    Affected if The function exists and lacks any 'current_user_can' or authorization check at its beginning
  4. Check for public access to the function
    Review the plugin code to see if the function is hooked to a public action or shortcode (such as 'wp_ajax_nopriv', 'add_action' with a public hook, or 'add_shortcode'), or test by making an unauthenticated HTTP request to the site with common WordPress AJAX endpoints
    Affected if The function is hooked to an action accessible to unauthenticated users (wp_ajax_nopriv_ or public hooks)
  5. Review WordPress error logs
    Check the wp-content/debug.log file (if debugging is enabled) or server access logs for requests triggering the moym_display_test_attributes function that originate from unauthenticated IP addresses
    Affected if Log entries show calls to the vulnerable function from non-authenticated sessions

The environment is affected if the YourMembership SSO Login plugin is installed with a version below 1.1.8 AND the moym_display_test_attributes function lacks capability verification and is publicly accessible.

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 plugin to version 1.1.8 or later which includes proper capability checks. Until then, consider disabling the plugin or restricting server-level access to prevent unauthenticated requests.

Recommended fix Moderate confidence

Version 1.1.8 or latest available version of YourMembership Single Sign On – YM SSO Login plugin

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'YourMembership Single Sign On – YM SSO Login' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 1.1.8 or higher

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-2025-10648 — 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-2025-10648 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