CVE-2025-48123
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 Generation of Code ('Code Injection') 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 Code Injection.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 confidenceCode injection vulnerability in the Spreadsheet Price Changer for WooCommerce plugin allows remote attackers to inject malicious code due to improper control of code generation. This critical flaw affects all versions up to and including 2.4.37, potentially enabling complete compromise of the WordPress site.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 installation and versionNavigate to Plugins > Installed Plugins in WordPress admin, or check the plugin folder /wp-content/plugins/spreadsheet-price-changer-for-woocommerce/ for the main PHP file and read its header comment to find the Version fieldAffected if The plugin is installed and the version is 2.4.37 or lower
-
Confirm plugin is activeCheck the WordPress admin Plugins page; the plugin must be active for the vulnerability to be exploitableAffected if The plugin status shows as 'Active'
-
Check for unauthorized PHP files in plugin directoryList all PHP files in /wp-content/plugins/spreadsheet-price-changer-for-woocommerce/ and compare against expected plugin files; look for unfamiliar filenames, especially those with encoded names, eval(), or base64_decode() patternsAffected if Unknown PHP files exist in the plugin directory or suspicious code patterns are found
-
Inspect uploads and temp directoriesCheck /wp-content/uploads/ and /wp-content/spreadsheet-price-changer-temp/ for newly created .php files, shell scripts, or executable files that were not intentionally uploadedAffected if Unexpected executable files are found in upload or temp directories
-
Review server access logs for plugin-related requestsSearch web server logs (Apache/Nginx access logs) for POST/GET requests to the plugin's PHP files, especially those containing unusual parameters, payload signatures, or repeated requests to the price changer functionalityAffected if Suspicious requests targeting the plugin are present in server logs
The environment is affected if the Spreadsheet Price Changer for WooCommerce plugin is installed, active, and running version 2.4.37 or lower, or if signs of unauthorized code execution are detected in plugin-related directories or logs.
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 dataImmediately update to the latest patched version when available, or disable the plugin if no update exists. Review server logs and file system for signs of compromise, as code injection may allow remote code execution.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48123 — 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-48123 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