Welcart E CommerceWordPress extension · Welcart
CVE-2023-43614
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 Order Data Edit page of Welcart e-Commerce versions 2.7 to 2.8.21 allows a remote unauthenticated attacker to inject an arbitrary script.
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 scripting (XSS) vulnerability in the Order Data Edit page of Welcart e-Commerce versions 2.7 through 2.8.21 allows a remote unauthenticated attacker to inject arbitrary JavaScript through unsanitized user input. The vulnerability has a CVSS score of 6.1 (MEDIUM), indicating moderate exploitability and impact.
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
>= 2.7, <= 2.8.21CVSS 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.
-
Identify Welcart e-Commerce versionNavigate to WordPress admin dashboard > Plugins > Welcart e-Commerce, or check the plugin file header at /wp-content/plugins/usc-e-shop/usc-e-shop.php for the 'Version' commentAffected if Installed version is >= 2.7 and <= 2.8.21
-
Confirm Order Data Edit page existsAccess the Order Data Edit page via WordPress admin: USc E-Shop > Order List, then click on any order to edit. Alternatively, the URL pattern is typically /wp-admin/admin.php?page=usces_orderlist&order_action=edit&order_id=IDAffected if The page is accessible and the plugin version falls within the vulnerable range
-
Verify unauthenticated access potentialTest if the Order Data Edit page or related order handling endpoints are accessible without login. The vulnerability states remote unauthenticated attackers can inject JavaScript, meaning no authentication should be required for exploitationAffected if The vulnerable page or its handling logic is accessible to unauthenticated users (this is the default behavior for the flaw)
If Welcart e-Commerce version is between 2.7 and 2.8.21 inclusive AND the Order Data Edit functionality is accessible (which is default), the environment is affected by this XSS vulnerability.
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 · scopedUpgrade to Welcart e-Commerce version 2.8.22 or later which contains the security patch. If immediate patching is not possible, restrict access to the Order Data Edit page to authenticated administrators only.
Welcart e-Commerce version 2.8.22 or later
- 1. Check current Welcart e-Commerce version installed on the system
- 2. Navigate to the Welcart official website or plugin administration panel
- 3. Look for and apply the latest security update, which should be version 2.8.22 or later
- 4. After upgrading, verify the fix by testing the Order Data Edit page for XSS vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Welcart E Commerce
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43614 — 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-2023-43614 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