dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-62045

HIGH · 8.1 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in CodexThemes TheGem Theme Elements (for WPBakery) thegem-elements.This issue affects TheGem Theme Elements (for WPBakery): from n/a through <= 5.10.5.1.

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 · moderate confidence

This is a PHP Remote File Inclusion (RFI) vulnerability in TheGem Theme Elements plugin for WPBakery Page Builder. The improper control of filenames in include/require statements allows attackers to control which files PHP executes, potentially enabling remote code execution by including malicious external PHP files.

MitigationUpdate TheGem Theme Elements to the latest patched version. If no patch is available, temporarily disable the plugin and audit server logs for signs of exploitation.

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

CVSS:3.1/AV:N/AC:H/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. Confirm TheGem Theme Elements plugin is installed
    Check your WordPress plugins directory for thegem-theme-elements or similar TheGem plugin folders, or list installed plugins via wp-cli: wp plugin list --status=active --format=csv
    Affected if TheGem Theme Elements plugin is present and active in the WordPress installation
  2. Identify the installed plugin version
    Inspect the main plugin PHP file for a version constant or comment, typically found in the plugin header section. Common paths include /wp-content/plugins/thegem-elements/ or /wp-content/themes/thegem/
    Affected if The version cannot be determined or is older than the patched version
  3. Verify WPBakery Page Builder is active
    Check if WPBakery Page Builder is installed and enabled on the same WordPress site. This is required for the vulnerable component to be accessible.
    Affected if WPBakery Page Builder is active and TheGem Theme Elements plugin is installed
  4. Review server access logs for RFI indicators
    Search web server logs (Apache/nginx) for suspicious requests to the vulnerable include/require paths. Look for patterns like ?file=http://, ?file=https://, or ../ directory traversal in parameters related to TheGem or WPBakery components.
    Affected if Log entries show external URLs or unusual file paths being requested through the plugin's include functions
  5. Audit plugin files for vulnerable include/require patterns
    If you have filesystem access, search plugin PHP files for include(), require(), include_once(), or require_once() calls where user-supplied parameters are used directly in the file path without validation.
    Affected if Direct use of request parameters in include/require statements is found without sanitization

A user is affected if TheGem Theme Elements plugin for WPBakery Page Builder is installed and its vulnerable include/require code paths are accessible without proper input validation.

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 TheGem Theme Elements to the latest patched version. If no patch is available, temporarily disable the plugin and audit server logs for signs of exploitation.

Recommended fix Moderate confidence

TheGem Theme Elements (for WPBakery) latest version (beyond 5.10.5.1)

  1. Check the current version of TheGem Theme Elements (for WPBakery) installed on your WordPress site
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins or Theme settings to verify current version is <= 5.10.5.1
  4. Update TheGem Theme Elements to the latest available version through WordPress admin or by downloading from the vendor
  5. After update, verify the new version number reflects the update
  6. Review theme settings after update to ensure functionality is intact
Caveat Minor: Review custom element configurations after upgrade as Visual Composer/WPBakery element settings may have changed

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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