CVE-2025-52812
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ApusWP Domnoo domnoo allows PHP Local File Inclusion.This issue affects Domnoo: from n/a through <= 1.49.
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 confidenceLocal File Inclusion vulnerability in ApusWP Domnoo allows attackers to include arbitrary local PHP files via unsanitized input in include/require statements, potentially leading to code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ApusWP Domnoo is installedCheck wp-content/themes/ or wp-content/plugins/ directory for Domnoo-related folders, or inspect the WordPress themes/plugins list via admin panel or databaseAffected if The Domnoo theme or plugin directory exists in the WordPress installation
-
Determine Domnoo versionOpen the main Domnoo PHP file (often the theme's functions.php or main plugin file) and locate the version constant/comment block, or check the WordPress theme/plugin admin pageAffected if The installed version is unknown or falls within an unpatched range
-
Identify vulnerable file inclusion codeSearch the Domnoo source code for include/require statements that use $_GET, $_POST, or $_REQUEST parameters without proper sanitization (e.g., include($_GET['file']) or require_once($path))Affected if Unsanitized file inclusion logic using user-controlled input is present in the codebase
-
Check if allow_url_include is enabledInspect PHP configuration (phpinfo() or php.ini) for the allow_url_include directiveAffected if allow_url_include is set to On (though this relates to remote file inclusion, it indicates insecure PHP configuration)
-
Test for LFI via HTTP parametersIf accessible, attempt a controlled test request with a benign local file path (e.g., ?file=../../../../wp-config.php) to a known Domnoo component that performs file inclusionAffected if The application returns content from the requested local file, confirming LFI is exploitable
A user is affected if ApusWP Domnoo is installed with vulnerable file inclusion code that uses unsanitized user input, allowing arbitrary local PHP file reads or execution.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version if available; otherwise, implement strict input validation and whitelist-based filtering on file inclusion parameters, ensuring allow_url_include is disabled in PHP configuration.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-52812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52812 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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