dbcve.org
Pie RegisterWordPress extension · Genetechsolutions

CVE-2024-13818

HIGH · 7.5 CVSS v3.1 Published 2025-02-21
Fix available
A fix is available. Upgrade to after 3.8.3.9 or later.
See remediation →
84/100
Remediation priority · High
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
The Registration Forms – User Registration Forms, Invitation-Based Registrations, Front-end User Profile, Login Form & Content Restriction plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.8.4 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information about users contained in the exposed log files.

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 WordPress user registration plugin creates log files that are stored in a publicly accessible web directory without proper access controls. Unauthenticated attackers can directly access these log files via HTTP requests, exposing sensitive user information such as registration data, credentials, or personal details recorded by the plugin.

MitigationMove log files outside the web root directory or restrict access via .htaccess/password protection. Update to the latest plugin version if a security patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pie RegisterWordPress extension
Affected:<= 3.8.3.9

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Pie Register plugin installation and version
    Navigate to WordPress admin dashboard > Plugins and locate 'Pie Register' in the installed plugins list. Check the version number displayed next to the plugin name, or inspect the plugin header in wp-content/plugins/pie-register/pie-register.php for the 'Version' field.
    Affected if The plugin is installed and the version is 3.8.3.9 or lower.
  2. Locate plugin log files in the file system
    Use a file manager or SSH to browse the WordPress installation. Check for log files in common locations: wp-content/plugins/pie-register/ directory, wp-content/uploads/pie-register/, or wp-content/. Look for files with .log, .txt extensions or names containing 'log', 'debug', or 'registration'.
    Affected if Log files exist in any directory under the WordPress web root.
  3. Verify log file accessibility via HTTP
    Attempt to access suspected log file URLs directly in a browser or via curl. Common paths include: /wp-content/plugins/pie-register/*.log, /wp-content/uploads/pie-register/*.log, or similar paths. Check if the file content is served instead of being blocked.
    Affected if The log file returns HTTP 200 and displays contents (registration data, usernames, emails, or other sensitive information) without authentication.
  4. Inspect log file contents for sensitive data
    If a log file is accessible, examine its contents for exposed data such as user registration details, email addresses, usernames, timestamps, or any personally identifiable information (PII).
    Affected if Log files contain user registration data, credentials, email addresses, or other sensitive information accessible to unauthenticated users.

If Pie Register version 3.8.3.9 or lower is installed and publicly accessible log files containing user data exist in the web root, the environment is vulnerable to CVE-2024-13818.

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
Upgrade available Upgrade to a release after 3.8.3.9
Interim mitigation

Move log files outside the web root directory or restrict access via .htaccess/password protection. Update to the latest plugin version if a security patch is available.

Recommended fix Moderate confidence

Pie Register 3.8.4 or latest stable release

  1. Check the current version of the Pie Register plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Pie Register and note the current version number
  4. If the installed version is 3.8.3.9 or lower, update to the latest available version
  5. Go to Plugins > Add New > Upload Plugin (if updating manually) or click Update Now if an update is available
  6. After updating, verify the new version number reflects the update
  7. Review any publicly accessible log files in the wp-content directory and ensure log files are not accessible via web browsers (consider moving them outside the web root or adding .htaccess rules to deny web access)

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

Fix this in Pie Register Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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