dbcve.org
All Post Contact FormWordPress extension · Rainbow Link

CVE-2024-50523

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-04
Fix available
A fix is available. Upgrade to after 1.7.3 or later.
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 RainbowLink Inc. All Post Contact Form allpost-contactform allows Upload a Web Shell to a Web Server.This issue affects All Post Contact Form: from n/a through <= 1.8.2.

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

Unrestricted file upload vulnerability in the All Post Contact Form WordPress plugin allows attackers to upload malicious PHP files (web shells) directly to the web server, enabling full remote code execution and complete system compromise.

MitigationUpdate All Post Contact Form to the latest patched version immediately. If no patch is available, disable the plugin or its file upload features, and consider removing the plugin entirely until a fix is released.

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
All Post Contact FormWordPress extension
Affected:<= 1.7.3

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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'All Post Contact Form' by Rainbow Link, or check the plugins directory at /wp-content/plugins/ for a folder containing 'all-post-contact-form' or similar
    Affected if The Rainbow Link All Post Contact Form plugin is present on the WordPress site
  2. Check the installed version
    In WordPress admin under Plugins, find the All Post Contact Form plugin and view its details to see the version number, or read the main plugin PHP file header for the 'Version' tag
    Affected if The installed version is 1.7.3 or lower
  3. Identify the upload endpoint
    Review the plugin source files in /wp-content/plugins/ for form handlers that process file uploads, typically looking for 'enctype="multipart/form-data"' in contact forms or $_FILES/$_POST handling in PHP files
    Affected if The plugin contains file upload functionality accessible through contact forms
  4. Inspect uploaded files directory
    Check the /wp-content/uploads/ folder (or custom upload directory) for any PHP files, .exe files, .phtml files, or other executable file types that should not be present
    Affected if Executable files (PHP, .exe, .phtml, .js with PHP code) are found in the uploads directory
  5. Review recent file modifications
    Check file modification timestamps in the uploads directory using 'ls -lt' or file manager to identify recently added executable files that may be web shells
    Affected if Newly created executable files exist in upload directories with recent timestamps

A user is affected if the Rainbow Link All Post Contact Form plugin version 1.7.3 or lower is installed and the file upload feature is active, with potentially malicious executable files present in the uploads folder.

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 1.7.3
Interim mitigation

Update All Post Contact Form to the latest patched version immediately. If no patch is available, disable the plugin or its file upload features, and consider removing the plugin entirely until a fix is released.

Recommended fix Moderate confidence

Latest version available (version > 1.8.2)

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate 'All Post Contact Form' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown, manually download the latest version from the WordPress Plugin Repository or vendor
  6. 6. Deactivate the current plugin version, then delete it
  7. 7. Upload and install the latest version of All Post Contact Form
  8. 8. Reactivate the plugin after installation
Caveat Review plugin settings and form configurations after upgrade as default behaviors may have changed

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

Fix this in All Post Contact Form Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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