CVE-2024-12849
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 · uneditedThe Error Log Viewer By WP Guru plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 1.0.1.3 via the wp_ajax_nopriv_elvwp_log_download AJAX action. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.
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 confidenceThe Error Log Viewer By WP Guru WordPress plugin versions up to 1.0.1.3 contains an unauthenticated arbitrary file read vulnerability via the wp_ajax_nopriv_elvwp_log_download AJAX action. Attackers can supply a path parameter to read any readable file on the server's filesystem, potentially exposing sensitive configuration files, credentials, or database credentials.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Error Log Viewer By WP Guru' (or 'WP Guru Error Log Viewer'). If not visible in admin, inspect the /wp-content/plugins/ directory for folders containing 'error-log-viewer' or 'wp-guru' in the name.Affected if The plugin folder exists in /wp-content/plugins/
-
Identify installed versionIn the WordPress plugins list, find the version number listed under the plugin name. Alternatively, open the main plugin PHP file (usually error-log-viewer.php or similar in the plugin folder) and look for the 'Version:' header in the plugin comment block.Affected if Version is 1.0.1.3 or any earlier version (the vulnerability affects versions up to and including 1.0.1.3)
-
Verify AJAX endpoint is reachableCheck if the WordPress site responds to the unauthenticated AJAX endpoint by making a request to: https://your-site.com/wp-admin/admin-ajax.php?action=elvwp_log_download. This endpoint should NOT be accessible to unauthenticated users.Affected if The AJAX action 'elvwp_log_download' responds to unauthenticated requests (no login required)
-
Test arbitrary file read capabilityIf you can access the endpoint, inspect whether a 'path' parameter is accepted and can be used to read arbitrary files on the server. Check the plugin's AJAX handler code for file read operations using the path parameter without proper validation.Affected if The plugin code accepts a 'path' parameter and reads files without sanitizing user input to prevent directory traversal
A user is affected if the Error Log Viewer By WP Guru plugin is installed with version 1.0.1.3 or earlier AND the elvwp_log_download AJAX action is accessible without authentication and accepts a path parameter for file reading.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a version beyond 1.0.1.3 once a patched release is available; alternatively, disable or remove the plugin immediately until a fix is released, as the unauthenticated nature means any site visitor can exploit this.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12849 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12849 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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