dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2023-47683

HIGH · 8.0 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Improper Privilege Management vulnerability in miniOrange WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn) allows Privilege Escalation.This issue affects WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn): from n/a through 7.6.6.

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 confidence

Improper privilege management in the miniOrange WordPress Social Login and Register plugin (versions through 7.6.6) allows attackers to escalate privileges via the social login authentication flow, potentially gaining administrative access to the WordPress site.

MitigationUpdate the miniOrange WordPress Social Login plugin to version 7.6.7 or later to remediate the privilege escalation vulnerability.

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 miniOrange Social Login plugin is installed
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'miniOrange WordPress Social Login and Register'
    Affected if The plugin is not present on the system (not affected)
  2. Determine installed plugin version
    In the Plugins list, click on the plugin to view its details, or if you have file access, check the main plugin file header in wp-content/plugins/miniorange-social-login/ for the Version comment
    Affected if The version number is 7.6.6 or lower (in the affected range)
  3. Check if social login is enabled
    Navigate to the plugin settings page in WordPress admin (usually under Users > Social Login or a dedicated miniOrange menu) and verify whether any social providers (Google, Facebook, Twitter, etc.) are configured and the login widget is active
    Affected if At least one social login provider is enabled and the feature is active on the site
  4. Identify social login users with elevated roles
    In WordPress admin > Users, examine user accounts. Look for users whose email domains match configured social providers, or check the plugin database tables for 'mo_openid' user meta indicating social login registration. Verify if any of these users hold the Administrator role
    Affected if There are social login users with Administrator or high-privilege roles on the site

If the installed plugin version is 7.6.6 or lower AND social login is enabled with at least one configured provider, the environment is vulnerable to the privilege escalation flaw.

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 miniOrange WordPress Social Login plugin to version 7.6.7 or later to remediate the privilege escalation vulnerability.

Recommended fix Moderate confidence

Latest version available from WordPress plugin repository or miniOrange (version higher than 7.6.6)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn)' by miniOrange.
  4. 4. Check if the current version is 7.6.6 or lower.
  5. 5. If yes, update the plugin to the latest available version from the WordPress plugin repository or from miniOrange.
  6. 6. Verify the update was successful by checking the plugin version number.
  7. 7. Test social login functionality to ensure the plugin still works correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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