dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-28394

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
An issue in Advanced Plugins reportsstatistics v1.3.20 and before allows a remote attacker to execute arbitrary code via the Sales Reports, Statistics, Custom Fields & Export module.

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

A remote code execution vulnerability exists in the Advanced Plugins reportsstatistics plugin versions 1.3.20 and prior. The vulnerability resides in the Sales Reports, Statistics, Custom Fields & Export module, likely due to improper input validation or insecure deserialization when processing report or export functionality, allowing unauthenticated attackers to execute arbitrary system commands.

MitigationImmediately update the reportsstatistics plugin to the latest version. If a patch is unavailable, disable the plugin entirely and remove it from the WordPress installation. Review server access logs for signs of exploitation and consider a forensic investigation if compromise is suspected.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate the reportsstatistics plugin files
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'reportsstatistics', 'reports-statistics', or similar variants containing 'reports' and 'statistics'. If using WP-CLI, run: wp plugin list --status=active --format=csv | grep -i report
    Affected if The plugin folder exists in the plugins directory and the plugin is active
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually reportsstatistics.php or similar in the plugin root) and look for the 'Version:' header in the plugin comment block. Alternatively, check readme.txt for the 'Stable tag:' entry
    Affected if The reported version is 1.3.20 or lower, or if the version cannot be determined (indicating an older or unmaintained installation)
  3. Verify the vulnerable module is accessible
    Check if the plugin exposes any REST API routes or admin-ajax.php endpoints related to 'sales-reports', 'statistics', 'export', or 'custom-fields'. Inspect the plugin code for any publicly accessible handlers handling report generation or data export functions
    Affected if The module handlers are reachable without authentication or with low-privilege user roles (subscriber/contributor)
  4. Inspect server access logs for exploitation indicators
    Review web server access logs (Apache/nginx) and WordPress access logs for POST/GET requests to the plugin's endpoints containing suspicious patterns like 'exec', 'system', 'passthru', 'base64_decode', or unusual command strings in URL parameters
    Affected if Log entries show requests to the reportsstatistics plugin endpoints with encoded payloads or shell command patterns
  5. Check for unexpected files or backdoors
    Scan the wp-content/uploads/ directory and the plugin folder for newly created PHP files with random names, encoded content, or files containing eval(), base64_decode(), or shell execution functions
    Affected if Suspicious PHP files exist in these directories that were not intentionally placed there

A user is affected if the reportsstatistics plugin version is 1.3.20 or prior and the Sales Reports/Statistics/Export module is installed and accessible.

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

Immediately update the reportsstatistics plugin to the latest version. If a patch is unavailable, disable the plugin entirely and remove it from the WordPress installation. Review server access logs for signs of exploitation and consider a forensic investigation if compromise is suspected.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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