CVE-2025-28947
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 MBStore - Digital WooCommerce WordPress Theme mbstore allows PHP Local File Inclusion.This issue affects MBStore - Digital WooCommerce WordPress Theme: from n/a through <= 2.3.
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 confidenceThe MBStore WordPress theme <= 2.3 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is not properly validated before being used in include/require statements. This allows authenticated or unauthenticated attackers to include arbitrary local PHP files, potentially leading to remote 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.
-
Identify if MBStore theme is installedCheck the WordPress themes directory at wp-content/themes/ for a folder named 'mbstore' or similarAffected if The mbstore theme folder exists in the WordPress themes directory
-
Determine the installed MBStore versionOpen wp-content/themes/mbstore/style.css and locate the 'Version:' header in the file commentsAffected if The version number is 2.3 or lower
-
Locate file inclusion code in the themeSearch theme PHP files for include, require, include_once, or require_once statements that use variables (e.g., include($_GET['...']) or include($var)) without proper sanitizationAffected if Unvalidated file inclusion code using user input is present
-
Identify accessible parametersReview theme PHP files for GET/POST parameters passed to file inclusion functions, check if they are accessible without authenticationAffected if File inclusion parameters are accessible to unauthenticated users or low-privilege authenticated users
-
Check for path traversal indicatorsTest or inspect the inclusion parameter for path traversal patterns (e.g., ../../) without validationAffected if The parameter accepts path traversal sequences without filtering
A user is affected if the MBStore theme version is 2.3 or lower AND unauthenticated or low-privilege users can access file inclusion parameters that accept unvalidated user 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 dataUpdate the MBStore theme to the latest version once available, or implement input validation with allowlist filtering on all file inclusion parameters to prevent path traversal attacks.
- 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-2025-28947 — 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-28947 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