dbcve.org
AerolandWordPress extension · Thememove

CVE-2025-14429

HIGH · 8.1 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to after 1.6.6 or later.
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 ThemeMove AeroLand aeroland allows PHP Local File Inclusion.This issue affects AeroLand: from n/a through <= 1.6.6.

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

ThemeMove AeroLand theme <= 1.6.6 contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly validates file path inputs used in include/require statements. This allows attackers to read sensitive local files on the server by manipulating file path parameters (e.g., passing ../../etc/passwd).

MitigationUpdate AeroLand theme to the latest patched version. As a temporary mitigation, implement strict whitelist-based validation on all file inclusion parameters and restrict file system access permissions. Consider deploying a WAF to block directory traversal patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AerolandWordPress extension
Affected:<= 1.6.6

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 AeroLand theme version
    Locate the theme's style.css or functions.php file within the wp-content/themes/aeroland directory and read the version header comment or theme version definition
    Affected if The version number returned is 1.6.6 or lower, or if no version is displayed (older unversioned releases)
  2. Find PHP files handling file inclusions
    Search the theme directory for PHP files containing include, include_once, require, or require_once statements that accept variables in the file path (e.g., include($var), include($_GET['param']))
    Affected if Any include/require statements directly use unsanitized request parameters or variables in file paths without validation
  3. Identify exposed file path parameters
    Examine URL parameters passed to PHP files in the theme (especially those doing file inclusions) by reviewing source code or testing with benign values
    Affected if Parameters accepting file paths are accessible via GET or POST requests without authentication
  4. Check for directory traversal filtering
    Review the code handling file path parameters to determine if it validates or sanitizes input, specifically looking for checks that block ../ sequences or absolute paths
    Affected if No validation exists to prevent directory traversal patterns like ../ or absolute paths such as /etc/passwd

You are affected if AeroLand theme version is 1.6.6 or lower AND the theme exposes file inclusion functionality with unvalidated path parameters accessible to attackers.

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
Upgrade available Upgrade to a release after 1.6.6
Interim mitigation

Update AeroLand theme to the latest patched version. As a temporary mitigation, implement strict whitelist-based validation on all file inclusion parameters and restrict file system access permissions. Consider deploying a WAF to block directory traversal patterns.

Recommended fix Moderate confidence

Latest stable Aeroland theme version (beyond 1.6.6) from ThemeMove

  1. Verify current Aeroland theme version in WordPress admin under Appearance > Themes
  2. Check ThemeMove official sources (thememove.com) for available updates to Aeroland theme
  3. If a newer version exists, update to the latest stable release from ThemeMove or your distribution source
  4. After updating, verify the fix by checking that the LFI vulnerability is no longer exploitable
  5. Consider using a Web Application Firewall (WAF) as an additional layer of protection until the update is applied

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

Fix this in Aeroland Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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