dbcve.org
AssemblyWordPress extension · Axiomthemes

CVE-2025-53447

HIGH · 8.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.1 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 axiomthemes Assembly assembly allows PHP Local File Inclusion.This issue affects Assembly: from n/a through <= 1.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

The Assembly theme by axiomthemes contains a PHP Local File Inclusion vulnerability where user-supplied input is used in include/require statements without proper validation or sanitization. An attacker could exploit this to read sensitive local files or potentially achieve remote code execution by including maliciously crafted files.

MitigationImplement strict input validation using whitelist approaches for file inclusion paths, use basename() and realpath() to sanitize and validate included files, and disable allow_url_include in PHP configuration.

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
AssemblyWordPress extension
Affected:<= 1.1

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. Locate the Assembly theme files
    Search for a directory named 'assembly' or 'axiomthemes-assembly' within your web server's theme directory (commonly wp-content/themes/ or sites/all/themes/)
    Affected if The Assembly theme by axiomthemes is installed on the server
  2. Determine the installed version
    Open the theme's style.css file or theme.json in a text editor and look for a 'Version:' header in the file comments, or check any version.php or version.txt file within the theme folder
    Affected if The version number is 1.1 or lower, or if no version is declared and the theme appears to be the original axiomthemes release
  3. Identify vulnerable include/require patterns
    Use grep or a text search to find all 'include', 'require', 'include_once', or 'require_once' statements in PHP files within the theme folder. Examine each to see if variables (such as $_GET, $_POST, or $_REQUEST) are used directly in the path without validation
    Affected if Any include/require statement uses unsanitized user input (e.g., include($_GET['page'];) without basename(), realpath(), or whitelist validation
  4. Check if vulnerable parameters are exposed
    Review the theme's PHP files to identify which $_GET, $_POST, or $_REQUEST parameters are passed to include/require statements, then determine if these parameters can be submitted via HTTP requests to your web application
    Affected if The vulnerable parameters are accessible via URL parameters or form inputs on any accessible page of the website
  5. Inspect the PHP configuration
    Create a PHP info file (<?php phpinfo(); ?)) temporarily or check your php.ini for the allow_url_include setting
    Affected if allow_url_include is enabled, which would allow inclusion of remote malicious files in addition to local files

You are affected if the Assembly theme version is 1.1 or lower AND the theme contains include/require statements using unsanitized user input that is accessible via web requests.

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

Implement strict input validation using whitelist approaches for file inclusion paths, use basename() and realpath() to sanitize and validate included files, and disable allow_url_include in PHP configuration.

Fix this in Assembly Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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