CVE-2025-48129
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 · uneditedIncorrect Privilege Assignment vulnerability in Holest Engineering Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light excel-like-price-change-for-woocommerce-and-wp-e-commerce-light allows Privilege Escalation.This issue affects Spreadsheet Price Changer for WooCommerce and WP E-commerce – Light: from n/a through <= 2.4.37.
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 confidenceAn Incorrect Privilege Assignment vulnerability in the Spreadsheet Price Changer for WooCommerce plugin allows authenticated users with low-level permissions (such as subscribers or customers) to escalate their privileges to administrator level, likely due to insufficient capability checks on administrative functions within the plugin.
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
- 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.
-
Verify plugin is installedNavigate to WordPress admin > Plugins and confirm 'Spreadsheet Price Changer for WooCommerce' is active, or inspect the wp-content/plugins directory for the plugin folderAffected if plugin is installed and active with a vulnerable version
-
Determine installed plugin versionIn WordPress admin > Plugins > Installed Plugins, find 'Spreadsheet Price Changer for WooCommerce' and read the version number from the plugin description; compare against any known fixed version if publicly availableAffected if installed version has not been patched for privilege escalation
-
Check for low-privileged user accountsIn WordPress admin > Users, review the list for accounts with Subscriber or Customer roles; these roles typically have minimal permissionsAffected if any subscriber or customer accounts exist in the system
-
Verify capability enforcement on admin functionsInspect the plugin source code (if accessible via file manager or FTP) for functions handling price changes or admin actions; look for missing capability checks like 'manage_options' before executing privileged operationsAffected if plugin code lacks proper capability checks before performing administrative actions
You are affected if the plugin is installed with a vulnerable version AND low-privileged user accounts (subscriber/customer) exist who could potentially access improperly secured admin functions.
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 plugin to the latest version as soon as a patch is released; in the interim, restrict access to this plugin by revoking user permissions or disabling the plugin entirely if unauthorized privilege escalation is suspected.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48129 — 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-48129 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