CVE-2023-37987
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 · uneditedMissing Authorization vulnerability in miniOrange YourMembership Single Sign On allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects YourMembership Single Sign On: from n/a through 1.1.3.
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 · moderate confidenceMissing Authorization vulnerability in miniOrange YourMembership Single Sign On plugin allows authenticated attackers to exploit incorrectly configured Access Control Security Levels. This broken access control issue enables users to access functionality or resources beyond their intended privilege level in the SSO authentication flow.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the miniOrange YourMembership SSO pluginCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'miniorange-ym-sso' or similar. Alternatively, query the WordPress database in the 'wp_options' table for option_name containing 'miniorange' and 'ym_sso' to confirm the plugin is active.Affected if The plugin folder or database record exists and is active on the site.
-
Determine the installed plugin versionOpen the main plugin file (usually miniorange-ym-sso.php) and look for the version comment header (e.g., 'Version: x.x.x'). Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' or version entry.Affected if The version is 1.1.3 or any version prior to the patched release.
-
Inspect Access Control Security Level settingsNavigate to the plugin settings page in the WordPress admin dashboard under 'miniOrange SSO -> YourMembership SSO -> SSO Settings' or similar. Look for a setting labeled 'Security Level', 'Access Control', 'Role Based Access', or 'Authorization Level' that controls which user roles can access specific SSO functions.Affected if The Security Level setting is configured to a value that allows lower-privileged users (such as subscribers or contributors) to access administrative or elevated SSO functions, or if the setting is present but enforces no role restrictions.
-
Verify authorization enforcement on SSO endpointsUse a low-privilege user account (e.g., a subscriber-level user) to attempt access to SSO configuration endpoints or trigger SSO actions that should be restricted to administrators. Inspect the plugin's PHP files for capability checks (e.g., 'manage_options', 'edit_users') before executing sensitive SSO functions.Affected if Low-privilege authenticated users can successfully access or modify SSO settings, initiate SP-initiated SSO requests, or retrieve user data without proper capability verification.
A site is affected if the miniOrange YourMembership SSO plugin is installed at version 1.1.3 or earlier AND the Access Control Security Level configuration permits authenticated users with lower privileges to access administrative or elevated SSO functionality.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the YourMembership SSO plugin (beyond 1.1.3) which contains proper authorization checks. If no patch available, restrict administrative access to the plugin settings and consider deploying a WAF rule to detect abnormal access patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37987 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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