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

CVE-2025-39406

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-19
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
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 mojoomla WPAMS apartment-management allows PHP Local File Inclusion.This issue affects WPAMS: from n/a through <= 44.0.

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 Local File Inclusion (LFI) vulnerability in the mojoomla WPAMS (WordPress Apartment Management System) plugin. The vulnerability stems from improper control of filenames used in include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code by including malicious local files.

MitigationImmediately upgrade WPAMS to the latest patched version (greater than 44.0). In the interim, disable the plugin if possible and review server configurations to restrict file access. The fix requires implementing strict input validation and allowlisting for any parameters used in include/require statements.

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

CVSS:3.1/AV:N/AC:L/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 WPAMS plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WPAMS' or 'WordPress Apartment Management System' by mojoomla
    Affected if WPAMS plugin is present in the plugins list, regardless of activation status
  2. Identify installed WPAMS version
    In the Plugins list, find WPAMS and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag
    Affected if Version number is 44.0 or lower (vulnerable); version is unknown but plugin is present (potentially vulnerable)
  3. Verify vulnerable include/require parameter
    Inspect HTTP requests to the site for parameters used in include() or require() statements, typically within the plugin's PHP files. Common parameter names in LFI flaws include 'page', 'file', 'path', 'template', or similar. Usegrep to search plugin source code for 'include(' or 'require(' with dynamic variable input
    Affected if Plugin code uses unsanitized parameters in include/require statements and those parameters are accessible via HTTP requests
  4. Test for LFI accessibility
    If a suspected parameter is found (e.g., ?file= or ?page=), attempt a safe test request with a benign path such as ../../../../etc/passwd or ../../wp-config.php to confirm the parameter allows path traversal
    Affected if The parameter successfully traverses directories or displays contents of files outside the intended directory
  5. Check plugin activation status
    In WordPress admin > Plugins, confirm whether WPAMS is currently activated. LFI impact is higher if the plugin is active and its endpoints are publicly accessible
    Affected if Plugin is activated and its vulnerable endpoints are reachable without authentication

You are affected if the WPAMS plugin is installed with version 44.0 or lower AND its vulnerable include/require parameter is accessible, allowing path traversal to potentially execute arbitrary PHP code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade WPAMS to the latest patched version (greater than 44.0). In the interim, disable the plugin if possible and review server configurations to restrict file access. The fix requires implementing strict input validation and allowlisting for any parameters used in include/require statements.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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