CVE-2024-26154
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 · uneditedAll versions of ETIC Telecom Remote Access Server (RAS) prior to 4.5.0 are vulnerable to reflected cross site scripting in the appliance site name. The ETIC RAS web server saves the site name and then presents it to the administrators in a few different pages.
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 confidenceReflected cross-site scripting (XSS) vulnerability in ETIC Telecom Remote Access Server allows injection of malicious scripts through the appliance site name parameter. The web server stores the site name and reflects it unsanitized across multiple admin pages, enabling session hijack or credential theft when administrators view affected pages.
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< 4.5.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.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.
-
Check installed firmware versionAccess the device admin console or check system information page to identify the current firmware version of ETIC Telecom Remote Access Server. Look for a version number displayed in the system status, about, or diagnostics section.Affected if The firmware version is below 4.5.0 (for example, 4.4.x, 4.3.x, etc.)
-
Locate site name configurationNavigate to the appliance administration interface and find the settings or configuration section where the site name parameter is defined. This may be in network settings, appliance settings, or general configuration.Affected if A site name parameter exists and is configurable in the admin interface
-
Verify web server reflects site nameAccess multiple admin pages within the RAS web interface and inspect whether the configured site name is displayed in the page content without visible encoding or sanitization.Affected if The site name appears in page output without HTML encoding (visible <, >, or script tags rendered as plain text indicates lack of sanitization)
-
Check admin page renderingSet a site name containing a benign test string such as <script>test</script> and navigate to several admin pages to observe if this literal string appears in the rendered HTML.Affected if The test string renders as visible text in the page HTML rather than being escaped or stripped
Your environment is affected if the ETIC Telecom RAS firmware version is below 4.5.0 AND the site name parameter is configured and reflected in the admin web interface without sanitization.
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 · scoped4.5.0
Upgrade ETIC Telecom RAS to version 4.5.0 or later to patch the XSS vulnerability. Until upgraded, restrict admin access to trusted users only and monitor for anomalous script injection attempts in the site name parameter.
4.5.0
- Backup the current RAS configuration before initiating the upgrade
- Download the Remote Access Server Firmware version 4.5.0 from ETIC Telecom's official support channels
- Access the ETIC RAS administrative interface and navigate to the firmware update section
- Upload and apply firmware version 4.5.0 following the vendor's standard upgrade procedure
- After reboot, verify the firmware version is 4.5.0 or later
- Log into the web interface and confirm the site name parameter is now properly sanitized to prevent XSS
- Test that the site name is displayed correctly on all admin pages without executing injected scripts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26154 — 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-2024-26154 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