dbcve.org
Wordpress Flash UploaderWordPress extension · Tinywebgallery

CVE-2014-5014

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-25
Fix available
A fix is available. Upgrade to 3.1.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
The WordPress Flash Uploader plugin before 3.1.3 for WordPress allows remote attackers to execute arbitrary commands via vectors related to invalid characters in image_magic_path.

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 Flash Uploader plugin before version 3.1.3 contains a command injection vulnerability in the image_magic_path parameter. Remote attackers can execute arbitrary operating system commands by supplying specially crafted input containing invalid characters that get passed to system calls without proper sanitization.

MitigationUpdate the WordPress Flash Uploader plugin to version 3.1.3 or later which contains the security fix. If an update is unavailable, remove the plugin entirely to eliminate the attack surface.

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
Wordpress Flash UploaderWordPress extension
Affected:< 3.1.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.0/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. Locate the Flash Uploader plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'tinywebgallery-flash-uploader', 'flash-uploader', or similar WordPress Flash Uploader plugin folders. Also check the wp-content/plugins/twg-flash-uploader/ directory if it exists.
    Affected if The plugin folder exists on the server
  2. Identify the plugin version
    Open the main plugin PHP file (usually includes/version.php, plugin.php, or index.php) and locate the version definition. Common locations: $version, $plugin_version, or Version: in the file header comments.
    Affected if The installed version is lower than 3.1.3 (e.g., 3.1.2, 3.1.1, 3.0.x, etc.)
  3. Verify the image_magic_path parameter is accessible
    Check the plugin configuration files (twg_*.php or config.php) for the image_magic_path parameter handling. Look for code that passes this parameter to system(), exec(), shell_exec(), or similar PHP functions without proper sanitization.
    Affected if The parameter is processed and passed to system calls without validation
  4. Check if the plugin is actively enabled
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether the Flash Uploader plugin shows as 'Active' or 'Network Active'.
    Affected if The plugin is enabled and running on the site

You are affected if the Tinywebgallery WordPress Flash Uploader plugin is installed and active with a version lower than 3.1.3, as the command injection vulnerability in the image_magic_path parameter can be exploited.

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 3.1.3 or later
Fixed in 3.1.3
Interim mitigation

Update the WordPress Flash Uploader plugin to version 3.1.3 or later which contains the security fix. If an update is unavailable, remove the plugin entirely to eliminate the attack surface.

Recommended fix High confidence

3.1.3

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to the WordPress admin dashboard, go to Plugins > Installed Plugins
  3. Find the WordPress Flash Uploader plugin and check the current version
  4. If the installed version is below 3.1.3, click 'Update Now' to upgrade to version 3.1.3 or later
  5. Alternatively, download version 3.1.3 or later from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version shows 3.1.3 or higher
  7. Test that the plugin functionality works correctly after the update

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

Fix this in Wordpress Flash Uploader Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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