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

CVE-2025-2101

HIGH · 8.1 CVSS v3.1 Published 2025-04-26
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
The Edumall theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.2.4 via the 'template' parameter of the 'edumall_lazy_load_template' AJAX action. This makes it possible for unauthenticated attackers to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where PHP files can be uploaded and included.

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 Edumall WordPress theme (versions up to 4.2.4) has an unauthenticated Local File Inclusion vulnerability in the 'edumall_lazy_load_template' AJAX action. The 'template' parameter is not sanitized, allowing attackers to include arbitrary PHP files and execute any PHP code on the server.

MitigationUpdate the Edumall theme to version 4.2.5 or later. If no update is available, disable the 'edumall_lazy_load_template' AJAX action and implement strict allowlist-based path validation for the template parameter.

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. Identify Edumall theme installation and version
    Locate the Edumall theme directory (typically /wp-content/themes/edumall/) and check the style.css or theme.json file for the version number, or query it via WordPress admin appearance section
    Affected if Edumall theme is installed and version is 4.2.4 or lower
  2. Verify the vulnerable AJAX action is exposed
    Test access to the AJAX endpoint by making a request to /wp-admin/admin-ajax.php with action=edumall_lazy_load_template, or check if this action is registered in the theme's functions
    Affected if The AJAX action 'edumall_lazy_load_template' is registered and accessible without authentication
  3. Confirm the template parameter is accepted
    Send a GET or POST request to the AJAX endpoint with action=edumall_lazy_load_template and a template parameter value (e.g., template=../../../../wp-config.php), then observe if the server attempts to include the file
    Affected if The server accepts and processes the template parameter without sanitization, allowing path traversal patterns

A user is affected if the Edumall theme version is 4.2.4 or lower and the unauthenticated edumall_lazy_load_template AJAX action is active and accepts arbitrary path values in the template parameter.

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 Edumall theme to version 4.2.5 or later. If no update is available, disable the 'edumall_lazy_load_template' AJAX action and implement strict allowlist-based path validation for the template parameter.

Recommended fix High confidence

Edumall theme version 4.2.5 or later

  1. Upgrade the Edumall WordPress theme to the latest available version from the vendor (thememove.com)
  2. Verify the upgrade by checking the theme version in WordPress admin under Appearance > Themes
  3. Confirm that the 'edumall_lazy_load_template' AJAX action no longer accepts arbitrary file paths in the 'template' parameter
  4. Ensure all other WordPress themes and plugins are updated as part of regular maintenance

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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