dbcve.org
Sel 411l FirmwareOperating system · Selinc

CVE-2023-2266

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An Improper neutralization of input during web page generation in the Schweitzer Engineering Laboratories SEL-411L could allow an attacker to generate cross-site scripting based attacks against an authorized and authenticated user. See product Instruction Manual Appendix A dated 20230830 for more details.

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

Cross-site scripting (XSS) vulnerability in the SEL-411L protection relay web interface where user-supplied input is not properly neutralized before being rendered in web pages. An authenticated attacker could inject malicious JavaScript that executes in the browser of other authorized users viewing the affected pages.

MitigationApply the vendor firmware update referenced in SEL Instruction Manual Appendix A (20230830). Until then, limit web interface access to trusted users only and monitor for suspicious script injection attempts.

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
Sel 411l FirmwareOperating system
Affected:>= r118-v0, < r118-v4>= r119-v0, < r119-v5>= r120-v0, < r120-v6>= r121-v0, < r121-v3>= r122-v0, < r122-v3>= r123-v0, < r123-v3>= r124-v0, < r124-v3>= r125-v0, < r125-v3>= r126-v0, < r126-v4>= r127-v0, < r127-v2= r128-v0= r129-v0

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. Identify device model
    Access the SEL-411L relay web interface or use the SEL ASCII protocol command 'METER' to confirm the device model is SEL-411L
    Affected if Device is not an SEL-411L relay, then this specific CVE does not apply
  2. Check firmware version
    In the web interface, navigate to the System > Software or About page to view the installed firmware version. Alternatively, use the SEL ASCII command 'VERSION' to retrieve the firmware version
    Affected if Firmware version cannot be determined, preventing comparison to affected ranges
  3. Compare version to affected ranges
    Match your installed firmware version (format rXXX-vY) against the affected ranges: r118-v0 to r118-v3, r119-v0 to r119-v4, r120-v0 to r120-v5, r121-v0 to r121-v2, r122-v0 to r122-v2, r123-v0 to r123-v2, r124-v0 to r124-v2, r125-v0 to r125-v2, r126-v0 to r126-v3, r127-v0 to r127-v1, r128-v0, or r129-v0
    Affected if Installed version falls within any of these ranges, the device is affected by this XSS vulnerability
  4. Confirm web interface is enabled
    In the relay settings, verify that the embedded web server (HTTP/HTTPS interface) is enabled under Communications > Web Server or equivalent configuration section
    Affected if Web interface is disabled, the attack surface for this XSS vulnerability is not accessible

The environment is affected if the device is an SEL-411L relay with the web interface enabled and a firmware version matching any of the listed affected ranges.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor firmware update referenced in SEL Instruction Manual Appendix A (20230830). Until then, limit web interface access to trusted users only and monitor for suspicious script injection attempts.

Recommended fix High confidence

r121-v3 (or the latest fixed version for your firmware branch: r118-v4, r119-v5, r120-v6, or r121-v3)

  1. 1. Identify the current firmware version of the SEL-411L device by accessing the device's web interface or using SEL ASCII commands.
  2. 2. Download the appropriate firmware update from selinc.com - select the fixed version that corresponds to your current firmware branch: r118-v4, r119-v5, r120-v6, or r121-v3.
  3. 3. Back up the current device configuration using the web interface or SEL-5037 AcSELerator Builder SEL-411L software.
  4. 4. Access the device firmware upgrade interface (typically found under Device > Firmware Update or similar in the web interface).
  5. 5. Upload the downloaded firmware file and initiate the upgrade process.
  6. 6. Wait for the upgrade to complete - do not power off the device during the update.
  7. 7. After reboot, verify the new firmware version matches the expected fixed version.
  8. 8. Restore the backed-up configuration if needed.
Caveat Firmware upgrades on protection relays may temporarily interrupt protection functions - plan during a maintenance window; always backup configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sel 411l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2266 — 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-2266 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