dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11085

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 WP Log Viewer plugin for WordPress is vulnerable to unauthorized use of functionality due to a missing capability check on several AJAX actions in all versions up to, and including, 1.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to access logs, update plugin-related user settings and general plugin 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 · high confidence

The WP Log Viewer plugin for WordPress fails to implement capability checks on multiple AJAX action handlers, allowing any authenticated user with Subscriber-level permissions or higher to execute these privileged actions. This enables unauthorized access to sensitive log files and modification of plugin settings.

MitigationUpdate WP Log Viewer to version 1.2.2 or later which implements proper capability checks on all AJAX actions.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 WP Log Viewer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Log Viewer' in the list. Note whether it is active or inactive.
    Affected if Plugin is installed and active
  2. Check installed plugin version
    Click on the plugin name in the Plugins page to view details, or inspect the plugin main file header in wp-content/plugins/wp-log-viewer/ for the 'Version' comment. Compare this to version 1.2.2.
    Affected if Version is present and is lower than 1.2.2
  3. Identify subscriber-level users
    In WordPress admin, go to Users and review the list. Check the Role column for any users assigned 'Subscriber' role.
    Affected if At least one user with Subscriber role exists
  4. Confirm AJAX endpoint accessibility
    Make an authenticated AJAX request to wp-admin/admin-ajax.php with a low-privilege (subscriber) user's nonce and action such as 'log_viewer_get_logs' or 'log_viewer_save_settings'. Inspect the response.
    Affected if Request returns successful data or allows settings modification without capability error
  5. Review user role capabilities
    Navigate to Users > Roles (if a role editor plugin is installed) or inspect the database table wp_usermeta for wp_capabilities to list all non-administrator roles.
    Affected if Subscriber or other low-privilege roles have access to privileged plugin actions

Environment is affected if WP Log Viewer plugin is installed with a version below 1.2.2 and there are subscriber-level users who can access the vulnerable AJAX actions.

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 WP Log Viewer to version 1.2.2 or later which implements proper capability checks on all AJAX actions.

Recommended fix Moderate confidence

Latest version after 1.2.1 (check wordpress.org for current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Log Viewer plugin
  4. Check if an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, you can manually download the updated plugin from wordpress.org/plugins/wp-log-viewer/ and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify that the plugin functions correctly and that unauthorized users can no longer access log files or modify settings

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-2024-11085 — 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-2024-11085 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