dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-10753

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-06
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 OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 6.26.14. This is due to missing capability checks and authentication verification on the OAuth redirect functionality accessible via the 'oauthredirect' option parameter. This makes it possible for unauthenticated attackers to set the global redirect URL option via the redirect_url parameter granted they can access the site directly.

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 OAuth SSO plugin for WordPress lacks capability checks and authentication verification on its OAuth redirect functionality exposed via the 'oauthredirect' option parameter. This allows unauthenticated attackers to set the global redirect URL option through the redirect_url parameter, potentially enabling phishing or open redirect attacks.

MitigationUpdate the plugin to version 6.26.15 or later which includes proper capability checks and authentication verification on the redirect functionality. Until updated, monitor for suspicious redirect_url parameter usage in 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Identify the OAuth SSO plugin and version
    Check WordPress installed plugins list or inspect the plugin header file (usually in wp-content/plugins/oauth-sso/oauth-sso.php) to read the Version: field
    Affected if The plugin is installed and the version is below 6.26.15 (or the version cannot be determined)
  2. Verify the redirect endpoint accepts unauthenticated requests
    Send a GET request to the site with parameter '?oauthredirect=1&redirect_url=https://example.com' and observe if the request is processed without requiring login
    Affected if The request completes without any authentication or capability check error
  3. Inspect the current redirect_url option value
    Query the WordPress options table (wp_options) for option_name = 'redirect_url' or check via admin: Settings > OAuth SSO > General Settings to see if redirect URL can be set
    Affected if The redirect_url option exists and can be set/modified by an unauthenticated user
  4. Check for recent unauthorized option changes
    Review WordPress audit logs or database option history for unexpected changes to redirect_url, oauth_redirect, or related options, especially from unauthenticated IP addresses
    Affected if The redirect URL option was changed without legitimate admin action or from unexpected sources

A user is affected if the OAuth SSO plugin is installed with a version prior to 6.26.15 AND the oauthredirect endpoint processes redirect_url parameters without requiring authentication.

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 6.26.15 or later which includes proper capability checks and authentication verification on the redirect functionality. Until updated, monitor for suspicious redirect_url parameter usage in requests.

Recommended fix Moderate confidence

6.26.15 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find the 'OAuth Single Sign On – SSO (OAuth Client)' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.26.15 or later
  5. 5. Alternatively, manually upload the fixed plugin version from wordpress.org/plugins/miniorange-oauth-social-login/

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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