CVE-2019-13633: Blinger.io v.1.0.2519 is vulnerable to Blind/Persistent XSS

This month

MEDIUM 6.1DOWNGRADE

CVE-2019-13633 is a medium-severity flaw (CVSS 6.1) affecting blinger. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Blinger.io v.1.0.2519 is vulnerable to Blind/Persistent XSS. An attacker can send arbitrary JavaScript code via a built-in communication channel, such as Telegram, WhatsApp, Viber, Skype, Facebook, Vkontakte, or Odnoklassniki. This is mishandled within the administration panel for conversations/all, conversations/inbox, conversations/unassigned, and conversations/closed.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-79
Published	2020-10-19
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: blinger

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-10-19 20:15 UTCPublished CVE record published
2026-06-17 02:17 UTCUpdated Record last modified

blinger blinger DOWNGRADE

Affected: 1.0.2519

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.2519

1. Check installed version

apt-cache policy blinger || rpm -q blinger || blinger --version

2. No fixed release: DOWNGRADE to a release before 1.0.2519 (Debian / Ubuntu)

apt-cache madison blinger sudo apt install blinger=<VERSION_BEFORE_1.0.2519> sudo apt-mark hold blinger

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list blinger sudo dnf downgrade blinger-<VERSION_BEFORE_1.0.2519> sudo dnf versionlock add blinger

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-13633?

blinger: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-13633 being exploited?

CVE-2019-13633 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-13633 affect?

CVE-2019-13633 affects blinger. Severity is medium (CVSS 6.1). Blinger.io v.1.0.2519 is vulnerable to Blind/Persistent XSS. An attacker can send arbitrary JavaScript code via a built-in communication channel, such as Telegram, WhatsApp, Viber, Skype, Facebook, Vkontakte, or Odnoklassniki. This is misha

How urgent is CVE-2019-13633?

Priority 42/100. Public exploit reference

Software pages

WhatsApp vulnerabilities · Telegram vulnerabilities

References

← Back to latest CVEs