CVE-2026-32963
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 · uneditedSD-330AC and AMC Manager provided by silex technology, Inc. contain a reflected cross-site scripting vulnerability. When a user logs in to the affected device and access some crafted web page, arbitrary script may be executed on the user's browser.
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 confidenceSD-330AC and AMC Manager web interfaces contain a reflected cross-site scripting (XSS) vulnerability. Attackers can inject malicious scripts through crafted URLs or web pages that execute in authenticated users' browsers, allowing session hijacking or credential theft.
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.50< 5.1.0CVSS 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.0/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 the product in useDetermine whether your environment contains either the Silextechnology SD-330AC device or the AMC Manager software. Check device labels, inventory records, or software listings.Affected if The product is SD-330AC or AMC Manager
-
Determine SD-330AC firmware versionAccess the SD-330AC web interface and navigate to the firmware or status page to view the currently installed firmware version. Alternatively, check the device documentation for CLI or management software methods to retrieve the version.Affected if The installed firmware version is lower than 1.50
-
Determine AMC Manager versionOpen AMC Manager and locate the version information, typically found in the About, Help, or System Information section of the application or its web interface.Affected if The installed AMC Manager version is lower than 5.1.0
-
Assess web interface exposureDetermine whether the web management interface for the device or software is accessible from network locations where untrusted users could potentially deliver malicious URLs. Check firewall rules, ACLs, or access restrictions.Affected if The web interface is accessible to untrusted users or networks and the version is below the fixed releases
You are affected if you have SD-330AC firmware below version 1.50 or AMC Manager below version 5.1.0, and the web management interface is accessible to potential attackers.
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 · scoped1.505.1.0
Apply vendor patch when available; until then, instruct users to avoid clicking untrusted links and consider network isolating the device management interface.
SD-330AC Firmware version 1.50 and AMC Manager version 5.1.0
- 1. Identify the current firmware version of the SD-330AC device by accessing the device's web management interface.
- 2. Identify the current version of AMC Manager installed on the system.
- 3. For SD-330AC: Download firmware version 1.50 or later from the official silex technology support website (www.silex.jp).
- 4. For AMC Manager: Download version 5.1.0 or later from the official silex technology support website (www.silex.jp).
- 5. Apply the firmware update to the SD-330AC device following the manufacturer's documented upgrade procedure.
- 6. Install AMC Manager version 5.1.0 or later on the affected system.
- 7. After updating, verify the new versions are correctly installed and the web management interface is accessible.
- 8. Test that the XSS vulnerability is remediated by attempting to inject malicious script via the identified attack vector (if known).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32963 — 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-32963 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