CVE-2025-13094
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 · uneditedThe WP3D Model Import Viewer plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the handle_import_file() function in all versions up to, and including, 1.0.7. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 confidenceThe WP3D Model Import Viewer WordPress plugin lacks file type validation in the handle_import_file() function, allowing authenticated users with Author-level access or higher to upload arbitrary files to the server, potentially enabling remote code execution.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the WP3D Model Import Viewer pluginCheck the WordPress plugins directory (wp-content/plugins/) for a folder named wp3d-models, wp3d-model-import-viewer, or similar containing the plugin filesAffected if The plugin folder exists in the WordPress installation
-
Determine the installed plugin versionOpen the main plugin PHP file and look for the version header in the plugin comment block, or check the readme.txt file for the Version fieldAffected if The version is 1.0.7 or lower (any version up to and including 1.0.7)
-
Identify the vulnerable handle_import_file functionSearch the plugin files for the function named handle_import_file() and examine its code for file type validation logicAffected if The function exists and lacks proper file type validation (no allowlist check for permitted file extensions)
-
Verify the upload endpoint is accessibleCheck WordPress admin for the plugin settings or scan plugin files for ajax actions or form handlers that call handle_import_fileAffected if The upload functionality is present and accessible to authenticated users with Author-level access or higher
A user is affected if the WP3D Model Import Viewer plugin is installed, the version is 1.0.7 or lower, and the handle_import_file function lacks file type validation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the WP3D Model Import Viewer plugin to version 1.0.8 or later which includes proper file type validation. If immediate update is not possible, restrict file upload capabilities and monitor for suspicious uploads.
Version 1.0.8 or latest available version
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WP3D Model Import Viewer
- Check if an update is available and update to the latest version
- If no update appears, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
- Verify the updated version is 1.0.8 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-13094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13094 in production — separate from our analysis above.
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.
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.
- 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