CVE-2025-32499
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 wpWax Logo Showcase Ultimate logo-showcase-ultimate allows PHP Local File Inclusion.This issue affects Logo Showcase Ultimate: from n/a through <= 1.4.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 · high confidenceThe wpWax Logo Showcase Ultimate WordPress plugin versions up to 1.4.4 contains a PHP Local File Inclusion (LFI) vulnerability. This improper control of filename for include/require statements allows authenticated attackers (with contributor-level access or higher) to include and execute arbitrary local PHP files, potentially leading to remote code execution or sensitive file disclosure.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Logo Showcase Ultimate plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Logo Showcase Ultimate' by wpWax, or check the /wp-content/plugins/logo-showcase-ultimate/ directory existsAffected if Plugin is installed and active
-
Check installed plugin versionIn WordPress admin Plugins list, click 'View Details' under Logo Showcase Ultimate, or read the version header from /wp-content/plugins/logo-showcase-ultimate/logo-showcase-ultimate.phpAffected if Version is 1.4.4 or lower (any version up to and including 1.4.4)
-
Confirm contributor or higher user role existsIn WordPress admin, go to Users and review user roles. Contributors and any role above Contributor (Author, Editor, Admin) can exploit this LFIAffected if At least one user account has Contributor, Author, Editor, or Administrator role
-
Inspect plugin for suspicious file modificationsCompare plugin files in /wp-content/plugins/logo-showcase-ultimate/ against a clean installation. Look for recently modified PHP files, especially in include/ or template/ directories, or any unfamiliar files added to the plugin folderAffected if Unknown files exist or files have been modified after the last legitimate update
Environment is affected if Logo Showcase Ultimate plugin version 1.4.4 or lower is installed, the plugin is active, and at least one user with Contributor-level access or higher exists.
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 Logo Showcase Ultimate to the latest version immediately. If no patched version is available, disable the plugin until a fix is released and audit for any signs of compromise.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32499 — 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-32499 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