dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-13062

HIGH · 8.8 CVSS v3.1 Published 2026-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The Supreme Modules Lite plugin for WordPress is vulnerable to arbitrary file upload in all versions up to, and including, 2.5.62. This is due to insufficient file type validation detecting JSON files, allowing double extension files to bypass sanitization while being accepted as a valid JSON file. 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 confidence

The Supreme Modules Lite WordPress plugin up to version 2.5.62 contains an arbitrary file upload vulnerability due to insufficient file type validation. The plugin detects and accepts files as valid JSON but fails to properly sanitize double extension files (e.g., malicious.php.json), allowing authenticated attackers with author-level access or higher to upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate the Supreme Modules Lite plugin to version 2.5.63 or later if available; if no update exists, disable the plugin or restrict upload capabilities to untrusted users until a patch is released.

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 checks

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

  1. Verify Supreme Modules Lite plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Supreme Modules Lite' in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%supreme-modules-lite%';
    Affected if Plugin is not found in the active plugins list
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Supreme Modules Lite, view the plugin details to see the version number; alternatively, check the plugin main PHP file header for 'Version:' tag or query: SELECT option_value FROM wp_options WHERE option_name LIKE '%supreme_modules_lite%version%';
    Affected if Version is 2.5.62 or lower (any version up to and including 2.5.62)
  3. Confirm author-level or higher user accounts exist
    Navigate to WordPress admin > Users and review user roles; query database: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%author%';
    Affected if At least one user account has author, editor, or administrator role
  4. Check if the upload functionality is accessible
    Review Supreme Modules Lite settings to determine if upload-related features (such as demo import, template upload, or media handling modules) are enabled; check plugin settings pages for any file import/upload options
    Affected if Upload features are enabled and accessible to users with author-level permissions

You are affected if the Supreme Modules Lite plugin is installed with version 2.5.62 or lower and author-level or higher user accounts can access the plugin's upload functionality.

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

Update the Supreme Modules Lite plugin to version 2.5.63 or later if available; if no update exists, disable the plugin or restrict upload capabilities to untrusted users until a patch is released.

Recommended fix Moderate confidence

Latest version of Supreme Modules Lite (higher than 2.5.62)

  1. 1. Log in to the WordPress admin dashboard with an account having administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Supreme Modules Lite' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the updated plugin from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the new version number reflects a version higher than 2.5.62

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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