dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-5814

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-07
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 Profiler – What Slowing Down Your WP plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpsd_plugin_control() function in all versions up to, and including, 1.0.0. This makes it possible for unauthenticated attackers to reactivate previously deactivated plugins after accessing the "Profiler" page.

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 Profiler plugin for WordPress lacks authorization checks on the wpsd_plugin_control() function, allowing unauthenticated users to reactivate any previously deactivated plugin by directly accessing the 'Profiler' page. This is a Broken Access Control vulnerability where the function performs privileged operations without verifying user capabilities.

MitigationAdd a capability check (e.g., current_user_can('manage_options')) at the beginning of the wpsd_plugin_control() function to ensure only authorized administrators can modify plugin states.

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 Profiler plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Profiler' or 'Profiler (wp-security-profiler)' plugin. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'profiler' or 'wp-security-profiler' in the name.
    Affected if The Profiler plugin is installed on the WordPress site
  2. Identify the installed Profiler plugin version
    In WordPress admin Plugins list, click on the plugin name to view details and find the version number. Or read the main plugin PHP file header for the 'Version' tag.
    Affected if The installed version lacks the authorization fix (version comparison unknown - check plugin changelog for security patches)
  3. Locate the wpsd_plugin_control function in plugin code
    Search the plugin files for the function 'wpsd_plugin_control' - typically in the main plugin PHP file or includes folder. Use grep or file search in /wp-content/plugins/{profiler-folder}/
    Affected if The function exists in the plugin code
  4. Inspect wpsd_plugin_control for authorization checks
    Open the file containing wpsd_plugin_control and examine the function body. Look for capability checks like current_user_can('manage_options') or wp_die() for unauthorized users near the beginning of the function.
    Affected if No capability check (current_user_can) or authorization gate is present at the start of wpsd_plugin_control
  5. Verify unauthenticated access to the Profiler page
    Open a browser incognito window and navigate directly to the Profiler page URL (typically /wp-admin/admin.php?page=profiler or similar). Attempt to access without logging in.
    Affected if The Profiler admin page loads or responds to unauthenticated requests

A user is affected if the Profiler plugin is installed AND the wpsd_plugin_control function lacks capability checks, allowing unauthenticated visitors to reactivate deactivated plugins.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a capability check (e.g., current_user_can('manage_options')) at the beginning of the wpsd_plugin_control() function to ensure only authorized administrators can modify plugin states.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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