CVE-2025-49935
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 xtemos WoodMart woodmart allows PHP Local File Inclusion.This issue affects WoodMart: from n/a through < 8.3.2.
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 confidenceLocal File Inclusion (LFI) vulnerability in the xtemos WoodMart WordPress theme allows attackers to include arbitrary PHP files from the server via improper control of filenames in include/require statements. This can lead to code execution, sensitive data exposure, or complete site compromise.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Confirm WoodMart theme is installedNavigate to WordPress admin dashboard > Appearance > Themes, or inspect the wp-content/themes/ directory for the woodmart folderAffected if WoodMart theme folder exists in the WordPress themes directory
-
Identify installed WoodMart versionCheck the style.css file inside wp-content/themes/woodmart/ for the 'Version:' header, or view theme details in WordPress admin under Appearance > ThemesAffected if A version number is displayed and it is below 8.3.2
-
Compare version against affected rangeCompare the identified version number to the fixed version 8.3.2 using standard version comparisonAffected if Installed version is lower than 8.3.2 (e.g., 8.3.1, 8.2.0, older)
-
Check for suspicious files in theme directoryReview wp-content/themes/woodmart/ for unfamiliar PHP files, especially in includes/ or files with random-looking names, using file manager or ls commandAffected if Unknown PHP files exist that were not part of the original theme distribution
-
Review access logs for LFI exploitation patternsSearch web server access logs (Apache/nginx) for requests containing '../', '..%2F', or paths like '/wp-content/themes/woodmart/include/' with suspicious file referencesAffected if Logs show requests attempting to include arbitrary files through the theme's include/require functions
If the WoodMart theme is installed and the version is below 8.3.2, the environment is vulnerable to CVE-2025-49935 and should be investigated further.
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.
dbcve · scopedUpdate WoodMart theme to version 8.3.2 or later. If patching is not immediately possible, disable the theme and review server access logs for signs of exploitation.
8.3.2
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to WordPress admin dashboard > Appearance > Themes
- 3. Locate the WoodMart theme and check for available updates
- 4. Update WoodMart theme to version 8.3.2 or later
- 5. Verify the update was successful by checking the theme version in Appearance > Themes
- 6. Test critical site functionality to ensure the update did not break any features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49935 — 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-49935 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