CVE-2025-32925
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 FantasticPlugins SUMO Reward Points rewardsystem allows PHP Local File Inclusion.This issue affects SUMO Reward Points: from n/a through <= 30.7.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 FantasticPlugins SUMO Reward Points WordPress plugin. The vulnerability allows attackers to manipulate file include statements to execute arbitrary PHP code from the local server, potentially leading to complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 30.7.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'SUMO Reward Points' or check the plugin's main PHP file header for the 'Version' comment. Alternatively, inspect the plugin folder 'wp-content/plugins/sumo-reward-points' and read the primary PHP file.Affected if The installed version is 30.7.0 or any lower version number.
-
Confirm plugin is activeVerify the SUMO Reward Points plugin is currently activated on the WordPress site. Check via WordPress admin Plugins page or inspect the 'wp_options' table for the active_plugins entry.Affected if The plugin is activated and running version 30.7.0 or lower.
-
Inspect for file inclusion patterns in plugin codeSearch the plugin directory for dynamic include/require statements using variable input. Look for patterns like 'include($_GET[...])', 'require($', or similar where request parameters are passed to file inclusion functions without sanitization.Affected if Code exists that uses unsanitized request parameters in include, require, include_once, or require_once functions.
-
Check PHP execution permissions in upload directoriesInspect the server configuration for upload folders (typically wp-content/uploads). Verify if .htaccess or server config allows PHP file execution in this directory. Check for any .php files that were uploaded.Affected if PHP execution is permitted in wp-content/uploads or similar writable directories, which would allow LFI to execute arbitrary code.
You are affected if the SUMO Reward Points plugin version is 30.7.0 or lower and the plugin is active, especially if your code contains vulnerable file inclusion logic or allows PHP execution in upload directories.
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 to a version beyond 30.7.0 if a patched release is available; otherwise, implement web application firewall rules to block directory traversal patterns in request parameters and disable PHP execution in upload directories.
- 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-32925 — 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-32925 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