CVE-2026-57360
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in eCommerce Product Catalog <= 3.5.4 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 · moderate confidenceUnauthenticated Cross-Site Scripting (XSS) vulnerability in eCommerce Product Catalog plugin versions 3.5.4 and below. An attacker can inject malicious JavaScript into vulnerable parameters without authentication, potentially stealing session cookies or performing actions on behalf of authenticated users.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify if eCommerce Product Catalog plugin is installedAccess WordPress admin dashboard, navigate to Plugins section, or check the wp-content/plugins directory for 'ecommerce-product-catalog' folderAffected if Plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > eCommerce Product Catalog and note the version number displayed, or check the main plugin PHP file for the 'Version' header commentAffected if Version is 3.5.4 or lower, or version cannot be determined but is implied to be pre-3.5.5
-
Verify if frontend product catalog is publicly accessibleVisit the site storefront or product listing pages without logging in to confirm unauthenticated access is possibleAffected if Product catalog pages are publicly reachable without authentication
-
Inspect web server access logs for suspicious request patternsReview access logs for unusual query parameters or form submissions containing JavaScript tags (<script>, javascript:, onerror=, etc.) targeting product-related endpointsAffected if Malicious XSS payloads are present in logged requests to product catalog URLs
Your environment is affected if eCommerce Product Catalog plugin versions 3.5.4 or below are installed and the product catalog is accessible to unauthenticated users, exposing vulnerable parameters to XSS injection.
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 eCommerce Product Catalog to version 3.5.5 or later. If immediate upgrade is not possible, implement web application firewall rules to block XSS attack patterns and sanitize user inputs.
- 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-2026-57360 — 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-2026-57360 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