dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-49671

CRITICAL · 9.9 CVSS v3.1 Published 2024-10-23
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 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 Dogu Pekgoz AI Image Generator for Your Content & Featured Images – AI Postpix ai-postpix allows Upload a Web Shell to a Web Server.This issue affects AI Image Generator for Your Content & Featured Images – AI Postpix: from n/a through <= 1.1.8.

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 AI Postpix WordPress plugin has an unrestricted file upload vulnerability allowing attackers to upload malicious PHP files (web shells) directly to the web server, enabling potential remote code execution. The plugin fails to properly validate file types and contents before saving uploaded files to accessible directories.

MitigationImmediately update the plugin to the latest version when available, or disable the plugin until a patch is released. Audit the uploads directory for any existing malicious PHP files and remove them. Implement proper server-side validation of file MIME type, extension, and content before allowing uploads.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify AI Postpix plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'AI Postpix' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list, indicating it is present in the environment.
  2. Identify installed AI Postpix version
    In WordPress admin, go to Plugins > Installed Plugins and locate AI Postpix. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/ai-postpix/ai-postpix.php for the 'Version' field.
    Affected if The installed version does not match the latest patched version released after this CVE, or version information cannot be confirmed as patched.
  3. Inspect uploads directory for PHP files
    Navigate to /wp-content/uploads/ (or your configured uploads directory) via FTP or file manager. Look for any .php files that were recently uploaded, especially in subdirectories with unexpected names.
    Affected if Any PHP files exist in the uploads directory, as this directory should only contain media files (images, documents) and never executable PHP scripts.
  4. Check server access logs for upload activity
    Review your web server access logs (Apache access.log, Nginx access.log) for POST requests to the plugin upload endpoint. Look for patterns like POST /wp-content/plugins/ai-postpix/ or uploads/ with file extensions .php.
    Affected if Evidence of .php files being uploaded via HTTP POST requests to the plugin functionality is found.
  5. Review plugin upload code configuration
    If you have file system access, examine the plugin files in /wp-content/plugins/ai-postpix/ for upload handling functions. Check if there is any file type validation or if the plugin allows direct PHP file uploads.
    Affected if The plugin code lacks proper file type validation (mime type check, extension whitelist) before saving uploaded files.

A user is affected if the AI Postpix plugin is installed and the installed version lacks the security fix for unrestricted file upload, or if PHP files are already present in the uploads directory.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update the plugin to the latest version when available, or disable the plugin until a patch is released. Audit the uploads directory for any existing malicious PHP files and remove them. Implement proper server-side validation of file MIME type, extension, and content before allowing uploads.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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