dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-52391

MEDIUM · 5.3 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 →
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
Missing Authorization 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 · moderate confidence

Missing Authorization vulnerability in the WordPress plugin Pie Register Premium allows attackers to access functionality they should not have permission to use, due to missing or insufficient access controls on certain operations.

MitigationUpdate to Pie Register Premium version 3.8.3.3 or later which contains the authorization fix. If immediate update is not possible, review plugin access controls and restrict administrative functions to authenticated administrators only.

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 Pie Register Premium is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Pie Register Premium' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active, exposing its functionality to potential unauthorized access.
  2. Check the installed plugin version
    Click on the plugin name in the Plugins list to view details, or open the main plugin file (typically /wp-content/plugins/pie-register-premium/pie-register.php) and look for the 'Version' header comment.
    Affected if The installed version is lower than 3.8.3.3, meaning the missing authorization fix is not present.
  3. Review user accounts for unauthorized administrative access
    Go to Users > All Users in WordPress admin and examine user roles. Check for any unexpected administrator accounts or users with 'administrator' role that you did not create.
    Affected if There are administrator accounts or elevated roles you did not authorize, which could indicate exploitation of the missing authorization flaw.
  4. Inspect server access logs for admin function access
    Review web server access logs (Apache error.log, Nginx access.log, or similar) for repeated requests to /wp-admin/admin-ajax.php, /wp-json/wp/v2/, or other plugin admin endpoints originating from unauthenticated or low-privilege IP addresses.
    Affected if Unauthenticated or non-administrator users are successfully accessing administrativeajax endpoints or plugin functions they should not reach.

You are affected if Pie Register Premium version 3.8.3.3 or lower is installed and active, or if unauthorized administrative access is detected in user accounts or access logs.

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 to Pie Register Premium version 3.8.3.3 or later which contains the authorization fix. If immediate update is not possible, review plugin access controls and restrict administrative functions to authenticated administrators only.

Recommended fix Moderate confidence

Pie Register Premium version 3.8.3.3 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins.
  3. 3. Locate Pie Register Premium in the installed plugins list.
  4. 4. Check if an update is available for Pie Register Premium.
  5. 5. If an update is available, update to version 3.8.3.3 or later.
  6. 6. Verify the update completed successfully by checking the plugin version in the Plugins list.
  7. 7. Test user registration functionality to ensure the plugin continues to work correctly after the update.
Caveat Review the plugin's changelog for version 3.8.3.3 to check for any changes that may affect your site configuration or customizations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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