CVE-2025-52723
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 codesupplyco Networker networker allows PHP Local File Inclusion.This issue affects Networker: from n/a through <= 1.2.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the codesupplyco Networker theme/plugin. The vulnerability exists due to improper validation of user-supplied input used in PHP include/require statements, allowing attackers to access sensitive local files on the server by manipulating file path parameters.
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.
-
Identify if Networker theme is installedCheck your WordPress themes directory (wp-content/themes/) for a folder named 'networker' or similar. Also check wp-content/plugins/ for a Networker plugin if distributed as a plugin.Affected if The Networker theme or plugin from codesupplyco is present in the WordPress installation
-
Determine the installed versionLocate the style.css file in the theme folder or a readme.txt in the plugin folder and check the Version: header. Alternatively, check any version.php or plugin.php file for version definitions.Affected if The version cannot be determined or is earlier than any patched version (no specific version range provided in CVE)
-
Locate PHP include/require statements using user inputSearch theme/plugin files for patterns like 'include($_GET', 'require($_POST', 'include($_REQUEST' or similar where user-supplied parameters are used directly in file inclusion functions without sanitization.Affected if Files contain include/require statements that directly use $_GET, $_POST, or $_REQUEST variables without validation
-
Identify the vulnerable parameterExamine the identified include/require code to find which URL parameter controls the file path (commonly parameters like 'page', 'file', 'path', 'template', 'include', or 'load').Affected if A URL parameter is used to control which file gets included without proper validation
-
Test for LFI vulnerabilityIf the vulnerable parameter is found, attempt to access a known file via the parameter (e.g., ?param=../../wp-config.php) to see if the server returns file contents. Only do this on authorized, non-production systems.Affected if The parameter accepts and returns contents of arbitrary local files outside the intended directory
A user is affected if they have the codesupplyco Networker theme or plugin installed and the vulnerable file inclusion code that uses unsanitized user input is accessible and exploitable.
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 dataImplement strict input validation using allowlists or basename() functions to sanitize file path parameters before use in include/require statements. Additionally, ensure magic_quotes or equivalent protections are in place and consider disabling allow_url_include.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52723 — 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-52723 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