dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-53822

CRITICAL · 10.0 CVSS v3.1 Published 2024-12-09
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
Unrestricted Upload of File with Dangerous Type vulnerability in Genetech Pie Register Premium.This issue affects Pie Register Premium: from n/a before 3.8.3.3.

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

Arbitrary file upload vulnerability in the Pie Register Premium WordPress plugin allows unauthenticated attackers to upload dangerous file types (e.g., PHP shells, malware) directly to the server without proper validation, potentially achieving remote code execution and complete system compromise.

MitigationUpdate Pie Register Premium to version 3.8.3.3 or later immediately. If immediate update is not possible, disable the plugin and review server for any recently uploaded suspicious files.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Check if Pie Register Premium is installed
    Look in the WordPress plugins directory (wp-content/plugins/) for a folder named 'pie-register-premium' or similar. In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for Pie Register Premium.
    Affected if The plugin is present in the environment
  2. Identify the installed version of Pie Register Premium
    In the WordPress admin, go to Plugins > Installed Plugins and find Pie Register Premium. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file header for the 'Version' field.
    Affected if The installed version is lower than 3.8.3.3 (e.g., 3.8.3, 3.8.2, 3.7.x, etc.)
  3. Inspect recent file uploads in the WordPress uploads directory
    Navigate to wp-content/uploads/ and examine files created recently, especially those with extensions like .php, .phtml, .php5, .php7, .phar, .js, or .exe. Check subdirectories for any unfamiliar files.
    Affected if Suspicious executable files (particularly PHP scripts) are found that were not intentionally uploaded by an administrator
  4. Review server access logs for file upload requests
    Examine web server access logs (Apache, Nginx) for POST requests to endpoints under /wp-content/uploads/ or plugin-related paths. Look for requests from unauthenticated IPs uploading files with dangerous extensions.
    Affected if Unauthenticated POST requests uploading .php or other executable file types are present in the logs
  5. Check for new admin accounts or modified user roles
    In WordPress admin, go to Users > All Users. Look for unfamiliar admin accounts or unexpected changes to user roles that may indicate the plugin vulnerability was exploited.
    Affected if New administrator accounts exist that were not created by known administrators

The environment is affected if Pie Register Premium is installed with a version lower than 3.8.3.3, and the plugin file upload functionality is enabled and accessible to unauthenticated users.

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 Pie Register Premium to version 3.8.3.3 or later immediately. If immediate update is not possible, disable the plugin and review server for any recently uploaded suspicious files.

Recommended fix High confidence

3.8.3.3

  1. 1. Backup your WordPress database and all files before proceeding.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate Pie Register Premium and deactivate it.
  5. 5. Delete the Pie Register Premium plugin.
  6. 6. Download Pie Register Premium version 3.8.3.3 from a trusted source.
  7. 7. Upload and install the new version through Plugins > Add New > Upload Plugin.
  8. 8. Reactivate the plugin.

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