dbcve.org
Welcart E CommerceWordPress extension · Welcart

CVE-2023-22705

MEDIUM · 6.1 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to after 2.8.10 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Collne Inc. Welcart e-Commerce plugin <= 2.8.10 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 confidence

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the Welcart e-Commerce plugin for WordPress. The flaw allows attackers to inject malicious JavaScript into URL parameters, which are then reflected back to users without proper sanitization or output encoding.

MitigationUpgrade to a patched version of the Welcart e-Commerce plugin (version 2.8.11 or later). Until patched, users should avoid clicking untrusted links to the site and site operators should implement WAF rules to filter XSS payloads in URL parameters.

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
Welcart E CommerceWordPress extension
Affected:<= 2.8.10

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Welcart e-Commerce plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for welcart folder
    Affected if Welcart e-Commerce plugin appears in the plugin list or filesystem
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Welcart e-Commerce and view the version number displayed, or check version in plugin header comment in main plugin PHP file
    Affected if Version displayed is 2.8.10 or lower
  3. Verify vulnerable URL parameter handling exists
    Test site by appending a benign test string like ?test=<script>alert(1)</script> to any Welcart page URL and inspect if the parameter value is reflected unescaped in the HTML response
    Affected if The test parameter value appears literally (unescaped) in the page source, indicating lack of output encoding

User is affected if Welcart e-Commerce plugin version 2.8.10 or lower is installed AND URL parameters are reflected without sanitization in page output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.8.10
Interim mitigation

Upgrade to a patched version of the Welcart e-Commerce plugin (version 2.8.11 or later). Until patched, users should avoid clicking untrusted links to the site and site operators should implement WAF rules to filter XSS payloads in URL parameters.

Fix this in Welcart E Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22705 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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