Welcart E CommerceWordPress extension · Welcart
CVE-2021-20734
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 scripting vulnerability in Welcart e-Commerce versions prior to 2.2.4 allows remote attackers to inject arbitrary script or HTML via unspecified vectors.
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 confidenceCross-site scripting (XSS) vulnerability in the Welcart e-Commerce WordPress plugin versions prior to 2.2.4 allows unauthenticated remote attackers to inject malicious JavaScript or HTML into web pages viewed by other users. The specific injection point(s) are not detailed in the advisory.
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
= 1.5.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Welcart e-Commerce plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Welcart e-Commerce' or check the plugin files in wp-content/plugins/ for the welcart directoryAffected if The plugin is present and active in the WordPress installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Welcart e-Commerce, and note the version number displayed. Alternatively, check the main plugin file header in wp-content/plugins/usc-e-shop/functions/version.php for the version constantAffected if The version shown is anything before 2.2.4 (any version including 1.5.2 through 2.2.3)
-
Confirm WordPress and PHP versions are compatible with the affected plugin rangeCheck your WordPress version in Dashboard > Updates and PHP version via phpinfo() or hosting control panelAffected if Any version combination where Welcart is below 2.2.4 regardless of WP/PHP versions
-
Review plugin configuration for input handlingNavigate to Welcart Settings in the WordPress admin panel and examine any fields that accept user input (customer information fields, product descriptions, order notes)Affected if The plugin version is below 2.2.4 and contains any active input fields accessible to unauthenticated users
You are affected if the Welcart e-Commerce plugin is installed and the version is any release prior to 2.2.4 (including version 1.5.2 specifically mentioned).
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 Welcart e-Commerce to version 2.2.4 or later to obtain the patched version. Review user accounts and content for any signs of malicious script injection that may have occurred prior to patching.
Fix this in Welcart E Commerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20734 — 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-2021-20734 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