CVE-2021-20735
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 ETUNA EC-CUBE plugins (Delivery slip number plugin (3.0 series) 1.0.10 and earlier, Delivery slip number csv bulk registration plugin (3.0 series) 1.0.8 and earlier, and Delivery slip number mail plugin (3.0 series) 1.0.8 and earlier) allows remote attackers to inject an arbitrary script by executing a specific operation on the management page of EC-CUBE.
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 three ETUNA EC-CUBE plugins (Delivery slip number, Delivery slip number CSV bulk registration, and Delivery slip number mail plugin, all 3.0 series) allows remote attackers to inject arbitrary JavaScript through a specific operation on the EC-CUBE management page.
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<= 1.0.10<= 1.0.8<= 1.0.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
- 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 installed ETUNA pluginsAccess EC-CUBE admin panel and navigate to the plugin management section, or inspect the plugin directory for files named 'delivery_slip' or similar related to the three affected pluginsAffected if Any of the three plugins (Delivery slip number, Delivery slip number CSV bulk registration, or Delivery slip number mail) are present in the installation
-
Check Delivery slip number plugin versionLocate the plugin version information in the plugin configuration file, composer.json, or within the plugin's main PHP file header where version is declaredAffected if The installed version is 1.0.10 or lower
-
Check Delivery slip number CSV bulk registration plugin versionLocate the plugin version information in the plugin configuration file, composer.json, or within the plugin's main PHP file header where version is declaredAffected if The installed version is 1.0.8 or lower
-
Check Delivery slip number mail plugin versionLocate the plugin version information in the plugin configuration file, composer.json, or within the plugin's main PHP file header where version is declaredAffected if The installed version is 1.0.8 or lower
-
Verify management page accessConfirm whether the delivery slip functionality is accessible to users with access to the EC-CUBE management console, particularly the input fields for delivery slip number dataAffected if The management page with delivery slip input fields is accessible and the plugin is actively processing user-submitted delivery slip data
A user is affected if any of the three ETUNA plugins are installed at the specified vulnerable versions and the delivery slip management functionality is accessible on the EC-CUBE admin page.
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 dataUpdate all three affected plugins to their patched versions: Delivery slip number plugin to 1.0.11 or later, Delivery slip number CSV bulk registration plugin to 1.0.9 or later, and Delivery slip number mail plugin to 1.0.9 or later. Alternatively, implement output encoding/sanitization on the management page inputs handling delivery slip data.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-20735 — 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-20735 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