CVE-2025-3280
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 · uneditedThe ELEX WooCommerce Advanced Bulk Edit Products, Prices & Attributes plugin for WordPress is vulnerable to SQL Injection via the 'attribute_value_filter' parameter in all versions up to, and including, 1.4.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 ELEX WooCommerce Advanced Bulk Edit plugin for WordPress versions up to 1.4.9 contains a SQL injection vulnerability in the 'attribute_value_filter' parameter. Authenticated attackers with Subscriber-level access can inject malicious SQL queries due to insufficient input escaping and lack of prepared statements in the existing SQL query, allowing extraction of sensitive database information.
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 the installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > ELEX WooCommerce Advanced Bulk Edit. Note the version number displayed and compare it to the affected range (versions up to and including 1.4.9).Affected if The installed version is 1.4.9 or earlier.
-
Confirm the plugin is activeCheck the plugins list in WordPress admin to ensure the ELEX WooCommerce Advanced Bulk Edit plugin is currently activated.Affected if The plugin is active and the version is 1.4.9 or earlier.
-
Check for Subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the user roles assigned. Look for any accounts with the Subscriber role.Affected if Subscriber-level users exist on the site and the vulnerable plugin version is active.
-
Inspect HTTP access logs for the vulnerable parameterReview web server access logs (Apache, Nginx) for requests to the WordPress site containing 'attribute_value_filter' in the query string or POST body.Affected if Requests using the attribute_value_filter parameter are being logged, indicating the feature is in use.
-
Verify WordPress REST API or admin AJAX endpointsCheck if the WordPress admin-ajax.php or wp-json API endpoints are accessible to authenticated users, as the SQL injection likely exploits these paths.Affected if The site allows authenticated requests (including Subscriber role) to processing endpoints.
A site is affected if it runs ELEX WooCommerce Advanced Bulk Edit version 1.4.9 or earlier, the plugin is active, and Subscriber-level user accounts can access the vulnerable parameter.
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 version 1.4.10 or later which addresses the SQL injection vulnerability by implementing proper input sanitization and prepared statements.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3280 — 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-3280 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