dbcve.org
Remote Management SystemApplication · Teltonika

CVE-2023-2587

HIGH · 8.3 CVSS v3.1 Published 2023-05-22
Fix available
A fix is available. Upgrade to 4.10.0 or later.
See remediation →
90/100
Remediation priority · Urgent
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
Teltonika’s Remote Management System versions prior to 4.10.0 contain a cross-site scripting (XSS) vulnerability in the main page of the web interface. An attacker with the MAC address and serial number of a connected device could send a maliciously crafted JSON file with an HTML object to trigger the vulnerability. This could allow the attacker to execute scripts in the account context and obtain remote code execution on managed devices.

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 confidence

Teltonika RMS versions before 4.10.0 have a stored XSS vulnerability in the main web interface page. An attacker with a target device's MAC address and serial number can inject malicious HTML/JavaScript via a crafted JSON file, leading to session hijacking and remote code execution on managed devices.

MitigationUpgrade Teltonika RMS to version 4.10.0 or later. Until then, restrict access to the RMS interface to trusted networks and monitor for suspicious JSON file imports.

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
Remote Management SystemApplication
Affected:< 4.10.0

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

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 the installed Teltonika RMS version
    Log into the RMS web interface and navigate to the System Information or About page. Alternatively, check the version via the RMS API or admin dashboard if available locally.
    Affected if The displayed version is below 4.10.0 (e.g., 4.9.x, 4.8.x, etc.)
  2. Confirm the JSON file import feature is present
    Locate the JSON import functionality in the RMS interface. This is typically found in the device provisioning, configuration backup/restore, or batch operations sections where users can upload configuration files.
    Affected if The JSON import feature exists and is accessible in the web interface, allowing crafted JSON files to be processed.
  3. Verify network accessibility of the RMS web interface
    Determine if the RMS web interface is exposed to untrusted networks. Check firewall rules, VPN configuration, or public IP binding that controls who can reach the login page.
    Affected if The RMS interface is accessible from networks outside the trusted internal network, making it reachable to potential attackers with MAC/serial number knowledge.

A user is affected if their Teltonika RMS installation is version 4.9.x or lower, the JSON import feature is enabled, and the interface is accessible to potential attackers who may possess device MAC addresses and serial numbers.

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
Upgrade available Upgrade to 4.10.0 or later
Fixed in 4.10.0
Interim mitigation

Upgrade Teltonika RMS to version 4.10.0 or later. Until then, restrict access to the RMS interface to trusted networks and monitor for suspicious JSON file imports.

Recommended fix High confidence

Teltonika Remote Management System version 4.10.0 or later

  1. 1. Back up the current Teltonika Remote Management System configuration and data
  2. 2. Download Teltonika Remote Management System version 4.10.0 or later from the official Teltonika vendor website
  3. 3. Follow the vendor's official upgrade procedure to install the update
  4. 4. Verify the upgrade was successful by checking the version number in the web interface

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

Fix this in Remote Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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