dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12579

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-27
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 Reuters Direct plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'logoff' action in all versions up to, and including, 3.0.0. This makes it possible for unauthenticated attackers to reset the plugin's settings.

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

The Reuters Direct WordPress plugin has a broken access control vulnerability where the 'logoff' action lacks a capability check, allowing any unauthenticated user to reset the plugin's settings to default. This is a classic Insecure Direct Object Reference (IDOR) / missing function level access control issue in the plugin's AJAX or admin action handlers.

MitigationUpdate to version 3.0.1 or later which includes the capability check, or add a capability verification check (e.g., current_user_can('manage_options')) to the 'logoff' action handler before processing the reset.

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. Confirm Reuters Direct plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Reuters Direct' or check the plugin files in /wp-content/plugins/ for a reuters-direct folder. Check the main plugin file for the version number defined in the plugin header.
    Affected if The plugin is installed and the version is lower than 3.0.1 or the version cannot be determined.
  2. Locate the logoff action handler
    Examine the plugin's PHP files for the function handling the 'logoff' action. Look for add_action or add_filter calls referencing 'logoff', and identify the callback function that processes the reset request.
    Affected if A handler exists that processes a 'logoff' or reset action without first verifying user capabilities.
  3. Verify capability check is missing
    In the logoff action handler function, search for a capability check such as current_user_can('manage_options') or similar authorization gate. If no such check exists before the settings reset logic, the vulnerability is present.
    Affected if The code performs the reset without any current_user_can() call or equivalent authorization check.
  4. Test unauthenticated access to logoff endpoint
    Send a request to the site's wp-admin/admin-ajax.php or admin-post.php with action=logoff (or the specific action name used by the plugin) without providing authentication credentials. Use a tool like curl or Burp to observe the response.
    Affected if The request completes successfully and resets plugin settings without returning an authentication error.

A user is affected if the Reuters Direct plugin version is below 3.0.1 and the logoff action can be triggered without authentication or capability 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 to version 3.0.1 or later which includes the capability check, or add a capability verification check (e.g., current_user_can('manage_options')) to the 'logoff' action handler before processing the reset.

Recommended fix High confidence

Latest version greater than 3.0.0 (check wordpress.org for exact current release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Reuters Direct' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the plugin version is greater than 3.0.0 after updating

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