CVE-2025-22533
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in bulktheme WOOEXIM wooexim allows SQL Injection.This issue affects WOOEXIM: from n/a through <= 5.0.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 · high confidenceSQL injection vulnerability in the WOOEXIM WordPress/WooCommerce plugin allows attackers to inject malicious SQL commands via unsanitized user inputs in certain parameters. The vulnerability exists in versions up to and including 5.0.0, enabling database compromise, data exfiltration, or privilege escalation.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
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.
-
Confirm WOOEXIM plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wooexim' or 'wooxim', or look for the plugin in the WordPress admin under Plugins > Installed Plugins.Affected if WOOEXIM plugin folder exists in the WordPress plugins directory
-
Identify the installed WOOEXIM versionOpen the main plugin file (typically wooexim/wooexim.php) and look for the 'Version' header in the plugin comment block at the top of the file, or check the version in the WordPress plugin admin UI.Affected if The Version field reads 5.0.0 or lower (e.g., 5.0.0, 4.9.x, 4.8.x, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm WOOEXIM shows as 'Active', or query the wp_options table for the option_name 'active_plugins' to see if wooexim is listed.Affected if WOOEXIM appears in the active_plugins list or shows as Active in the admin panel
-
Check for user-facing input formsReview the WOOEXIM plugin settings pages and any public-facing export/import features that accept user input (such as product export, order export, or parameter filters). These forms typically handle data that gets passed to database queries.Affected if Any WOOEXIM feature that accepts user input (search fields, filter parameters, export options) is accessible on the site
The environment is affected if WOOEXIM plugin is installed with version 5.0.0 or lower and the plugin (or any of its input-handling features) is active on the WordPress site.
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 dataUpgrade WOOEXIM to a patched version beyond 5.0.0, or implement parameterized queries/prepared statements for all database queries handling user input.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22533 — 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-22533 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