CVE-2023-25999
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 snstheme BodyCenter - Gym, Fitness WooCommerce WordPress Theme allows PHP Local File Inclusion. This issue affects BodyCenter - Gym, Fitness WooCommerce WordPress Theme: from n/a through 2.4.
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 confidenceA PHP file inclusion vulnerability in the BodyCenter WordPress theme allows attackers to include arbitrary files via insufficiently validated user input to PHP include/require statements. This can lead to remote code execution through local file inclusion (LFI) and potentially remote file inclusion (RFI) depending on server configuration.
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 BodyCenter theme is installedLog into WordPress admin panel, navigate to Appearance > Themes, and look for the BodyCenter theme in the list of installed themes. Alternatively, check the /wp-content/themes/bodycenter/ directory via file system access.Affected if The BodyCenter theme appears in the installed themes list.
-
Determine BodyCenter theme versionOpen the style.css file in the theme directory (/wp-content/themes/bodycenter/style.css) and locate the 'Version:' header in the CSS comment block at the top. Alternatively, check theme.json if present for version information.Affected if The version number displayed is lower than the patched version provided by the theme developer.
-
Identify vulnerable file inclusion codeSearch the theme's PHP files for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without proper sanitization. Common patterns to look for: include($_GET['parameter']), require($var), etc.Affected if Theme PHP files contain include/require statements using unsanitized user input from request parameters.
-
Check for actual exploitation attemptsReview web server access logs (typically in /var/log/nginx/access.log or /var/log/apache2/access.log) for directory traversal patterns in requests, such as '../', '..\', or absolute file paths in query parameters that may target theme files.Affected if Logs show requests containing directory traversal sequences (../ or ..\) directed at theme-related PHP endpoints.
A user is affected if the BodyCenter theme is installed and the version is lower than the patched version, especially if the theme code contains file inclusion logic using unsanitized user-supplied input.
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 dataUpgrade to the latest version of the BodyCenter theme. If no patch is available, disable the theme or implement web application firewall rules to block directory traversal patterns in request parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25999 — 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-2023-25999 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