dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-7617

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-24
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 Secufor_OAuth plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to disconnect the WordPress site from its linked Secufor account by clearing the plugin's stored login token and user login configuration.

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 Secufor_OAuth WordPress plugin lacks proper authorization checks on an action that disconnects the site from its Secufor OAuth account. Unauthenticated attackers can directly invoke this action to clear stored login tokens and user login configuration, effectively severing the OAuth connection without any credentials.

MitigationUpdate the plugin to the latest version once available, or implement proper capability checks and nonce validation on the disconnection function to verify user authorization before allowing token/configuration changes.

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. Verify Secufor_OAuth plugin installation
    Check the WordPress plugins directory for the Secufor_OAuth plugin folder, or query the wp_plugins database table for the plugin name
    Affected if The plugin is installed and active in WordPress
  2. Locate the OAuth disconnection handler
    Search plugin files for functions that handle OAuth disconnection or token clearing, typically named with terms like disconnect, logout, unlink, or remove connection
    Affected if A disconnection handler function exists in the plugin code
  3. Inspect disconnection function for authorization checks
    Examine the disconnection handler code for capability checks (current_user_can), nonce validation (check_ajax_referer or wp_verify_nonce), or any current_user check before executing the disconnect action
    Affected if The function lacks capability checks, nonce validation, or user authentication verification before clearing tokens
  4. Test unauthenticated access to disconnection action
    Attempt to invoke the disconnection action via direct URL request (such as wp-admin/admin-ajax.php with appropriate action parameter, or a dedicated disconnect endpoint) without providing authentication credentials
    Affected if The disconnection action executes successfully without requiring authentication
  5. Confirm token configuration clearing occurred
    Check the WordPress options database table or plugin settings for removal of OAuth tokens, user mappings, or connection status flags after triggering the disconnection
    Affected if OAuth tokens and connection configuration are cleared or removed after the action

A user is affected if the Secufor_OAuth plugin is installed and the disconnection function can be triggered without any authentication or authorization verification.

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 the latest version once available, or implement proper capability checks and nonce validation on the disconnection function to verify user authorization before allowing token/configuration changes.

Recommended fix Moderate confidence

Version 1.0.8 or later

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the Secufor_OAuth plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to the latest version (1.0.8 or later).
  5. 5. If no update is visible in the WordPress admin, manually download the latest version from the WordPress Plugin Repository at plugins.trac.wordpress.org and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is working correctly and test the Secufor OAuth connection.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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