Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-4103: Cryptocat before 2.0.22 has Remote Script Injection due to improperly sanitizing user input

68
This week
CRITICAL 9.8REMOTEUPGRADE

CVE-2013-4103 is a critical-severity flaw (CVSS 9.8) affecting cryptocat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Cryptocat before 2.0.22 has Remote Script Injection due to improperly sanitizing user input

Why this priority

  • Critical severity
  • EPSS top 6%: very likely to be exploited
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance6.9% (top 6%)
CISA exploited listNo
WeaknessCWE-20
Published2019-11-04
Last modified2026-06-16
Publisher (CNA): Red Hat, Inc. · Vendor: cryptocat project

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

cryptocat project cryptocat UPGRADE
Affected: < 2.0.22
Fixed in: 2.0.22
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy cryptocat || rpm -q cryptocat || cryptocat --version
2. UPGRADE to 2.0.22 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade cryptocat
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade cryptocat
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-2013-4103?

cryptocat: upgrade to 2.0.22. Exact commands for each OS are on this page.

Is CVE-2013-4103 being exploited?

CVE-2013-4103 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-2013-4103 affect?

CVE-2013-4103 affects cryptocat. Severity is critical (CVSS 9.8). Cryptocat before 2.0.22 has Remote Script Injection due to improperly sanitizing user input

How urgent is CVE-2013-4103?

Priority 68/100. Critical severity; EPSS top 6%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.