dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2012-10026

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-05
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
Public exploit 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 plugin Asset-Manager version 2.0 and below contains an unauthenticated arbitrary file upload vulnerability in upload.php. The endpoint fails to properly validate and restrict uploaded file types, allowing remote attackers to upload malicious PHP scripts to a predictable temporary directory. Once uploaded, the attacker can execute the file via a direct HTTP GET request, resulting in remote code execution under the web server’s context.

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 Asset-Manager plugin version 2.0 and below contains an unauthenticated arbitrary file upload vulnerability in upload.php. The endpoint fails to validate or restrict uploaded file types, allowing remote attackers to upload malicious PHP scripts to a predictable temporary directory. These uploaded files can then be executed via direct HTTP GET request, achieving remote code execution under the web server's context.

MitigationRemove or disable the vulnerable Asset-Manager plugin immediately; if the plugin functionality is required, seek an updated patched version from the vendor or replace with a secure alternative.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify if WordPress is present
    Look for wp-config.php in the web root or check for WordPress-specific file structures and tables in the database
    Affected if The target is not a WordPress installation - this CVE does not apply
  2. Locate the Asset-Manager plugin
    Check the wp-content/plugins/ directory for a folder named 'asset-manager' or 'asset_manager'. Also check the WordPress plugin admin panel for an installed plugin named 'Asset Manager'
    Affected if The Asset-Manager plugin is not installed - this CVE does not apply
  3. Determine the plugin version
    Open the main plugin file (usually asset-manager.php or similar in the plugin folder) and look for a version comment or header. Alternatively, check the plugin details in the WordPress admin panel
    Affected if The installed version is 2.0 or lower, or version information cannot be determined (assume affected)
  4. Verify the vulnerable upload.php exists
    Check for the presence of upload.php within the asset-manager plugin directory (wp-content/plugins/asset-manager/upload.php)
    Affected if The upload.php file exists in the plugin directory - the file upload vector is present
  5. Confirm the plugin is active
    Check the WordPress database wp_options table for option_name 'active_plugins', or use the plugin admin panel to verify if Asset Manager is currently enabled
    Affected if The Asset-Manager plugin is active - the vulnerability is reachable

If WordPress is running with Asset-Manager plugin version 2.0 or below in an active state, the environment is affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or disable the vulnerable Asset-Manager plugin immediately; if the plugin functionality is required, seek an updated patched version from the vendor or replace with a secure alternative.

Recommended fix Moderate confidence
  1. 1. Identify if the Asset-Manager plugin is still installed on any WordPress sites.
  2. 2. If the plugin is present, immediately deactivate and delete it from all affected WordPress installations.
  3. 3. Search the WordPress plugin repository (wordpress.org) for 'Asset Manager' to confirm whether the plugin still exists or has been removed.
  4. 4. If the plugin was a core functionality requirement, identify a reputable alternative WordPress plugin from the official repository that provides similar asset management features.
  5. 5. After removal, audit the WordPress installation for any suspicious PHP files in the wp-content/uploads/ directory and other writable directories.
  6. 6. Review web server access logs for any POST requests to upload.php or similar endpoints that may indicate exploitation attempts.
Caveat The plugin has likely been removed from the WordPress plugin repository and no longer receives updates. If the plugin was required for site functionality, a replacement must be found.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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