Product Gallery Slider For WoocommerceWordPress extension · Codeixer
CVE-2022-45372
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Codeixer Product Gallery Slider for WooCommerce plugin <= 2.2.8 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Codeixer Product Gallery Slider for WooCommerce plugin versions 2.2.8 and below. The flaw allows attackers to trick authenticated administrators into performing unintended actions via malicious requests.
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
Product Gallery Slider For WoocommerceWordPress extension
<= 2.2.8CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installationNavigate to WordPress admin > Plugins and locate 'Codeixer Product Gallery Slider for WooCommerce', or inspect the plugin directory at wp-content/plugins/codeigner-product-gallery-slider-for-woocommerce/ and check the main plugin file for the version headerAffected if the plugin is installed in your WordPress environment
-
Identify installed versionRead the version number from the plugin's main PHP file (typically contains 'Version: x.x.x' in the header comment) or view the version displayed in the WordPress Plugins admin pageAffected if a version number is displayed for this plugin
-
Compare against vulnerable rangeCompare your installed version number to 2.2.8 - treat the version as a decimal (e.g., 2.2.8 equals 2.28, 2.2.7 equals 2.27) or use semantic versioning comparisonAffected if the installed version is 2.2.8 or any version lower than 2.2.8 (e.g., 2.2.7, 2.2.6, 2.0.0, 1.0.0)
You are affected if the Codeixer Product Gallery Slider for WooCommerce plugin is installed and its version is 2.2.8 or lower.
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.
dbcve · scopedUpdate to version 2.2.9 or later which contains the security fix. Until patched, admin sessions should not be left unattended and administrators should be cautious of clicking links in untrusted emails.
Latest version available on WordPress plugin repository (version > 2.2.8)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find Product Gallery Slider for WooCommerce
- If an update is available, click 'Update Now' to update to the latest version
- Alternatively, manually download the latest version from wordpress.org/plugins/product-gallery-slider-for-woocommerce and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Product Gallery Slider For Woocommerce
Scoped from the published advisory
- 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-2022-45372 — 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-2022-45372 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