Unrestricted File UploadWeakness · CWE-434

CVE-2024-50494

CRITICAL · 10.0 CVSS v3.1 Published 2024-10-29

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

NVD · unedited

Unrestricted Upload of File with Dangerous Type vulnerability in Amin Omer Sudan Payment Gateway for WooCommerce wc-sudan-payment-gateway allows Upload a Web Shell to a Web Server.This issue affects Sudan Payment Gateway for WooCommerce: from n/a through <= 1.2.2.

Technical summary

dbcve analysis · high confidence

The Sudan Payment Gateway for WooCommerce plugin (wc-sudan-payment-gateway) versions 1.2.2 and below contains an unrestricted file upload vulnerability. The plugin fails to properly validate or restrict the types of files that users can upload through the payment gateway interface, allowing attackers to upload malicious PHP files (web shells) directly to the web server. Once uploaded, these web shells can be executed to achieve remote code execution, potentially giving attackers full control of the affected WordPress site.

MitigationUpdate the plugin to the latest version immediately. If no patch is available, disable the plugin until a fix is released. The remediation requires implementing strict file type validation (extension and MIME type whitelist) for all uploaded files, storing uploads outside the webroot, and disabling script execution in upload directories.

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

CVSS breakdown

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?

dbcve checks

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

Verify the Sudan Payment Gateway plugin is installed

Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'wc-sudan-payment-gateway' or 'sudan-payment-gateway'. In WordPress admin, go to Plugins > Installed Plugins and look for 'Sudan Payment Gateway for WooCommerce'.

Affected if The plugin folder exists in your plugins directory and the plugin is active in WordPress.
Identify the installed plugin version

Open the main plugin PHP file (typically the plugin root file) and locate the version comment header (e.g., 'Version: x.x.x'). Alternatively, in WordPress admin, find the plugin in the plugins list and hover over it to see the version number displayed.

Affected if The installed version is 1.2.2 or any version lower than 1.2.2.
Confirm the payment gateway is enabled in WooCommerce

In WordPress admin, navigate to WooCommerce > Settings > Payments. Check if 'Sudan Payment Gateway' or a similar entry is listed and enabled. Look for any payment method toggle set to 'enabled'.

Affected if The Sudan Payment Gateway payment method is enabled in WooCommerce settings, allowing customers to use this checkout option.
Inspect the file upload implementation

Examine the plugin files for functions handling file uploads. Look for PHP code that processes uploaded files through the payment form, checking if the plugin accepts file attachments or payment document uploads. Search for 'move_uploaded_file', 'wp_upload_bits', or similar file handling functions.

Affected if The plugin contains file upload functionality that processes files submitted through the payment gateway interface without proper validation.
Check the upload directory configuration

Review the plugin settings or code to determine where uploaded files are stored. Common locations include wp-content/uploads/, the plugin directory itself, or a subdirectory within it. Verify if uploads are stored inside the webroot.

Affected if Uploaded files are stored in a directory accessible via web browser (inside webroot) and script execution is not disabled for that directory.

You are affected if the Sudan Payment Gateway for WooCommerce plugin is installed at version 1.2.2 or below, the payment gateway is enabled in WooCommerce, and the plugin accepts file uploads without proper validation.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the plugin to the latest version immediately. If no patch is available, disable the plugin until a fix is released. The remediation requires implementing strict file type validation (extension and MIME type whitelist) for all uploaded files, storing uploads outside the webroot, and disabling script execution in upload directories.

Recommended fix Low confidence

Latest version available in WordPress plugin repository (version higher than 1.2.2)

1. Check the current version of the Sudan Payment Gateway for WooCommerce plugin installed on your WordPress site
2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
3. Locate 'Sudan Payment Gateway for WooCommerce' and verify the version number
4. If the installed version is <= 1.2.2, update the plugin to the latest available version from the WordPress plugin repository
5. After updating, verify the file upload functionality is properly restricted to expected file types only
6. Check for any web shells or suspicious files that may have been uploaded prior to the fix

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

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

12.0 hours of engineering $2,080

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50494 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-50494?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 10.0 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 12 hrs · Moderate

Typical engagement from $2,080

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-50494 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References