CVE-2011-1933: SQL injection vulnerability in Jifty::DBI before 0.68.

Q: How do I fix CVE-2011-1933?

\: upgrade to 0.68. Exact commands for each OS are on this page.

Q: Is CVE-2011-1933 being exploited?

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

Q: What does CVE-2011-1933 affect?

CVE-2011-1933 affects \. Severity is critical (CVSS 9.8). SQL injection vulnerability in Jifty::DBI before 0.68.

Q: How urgent is CVE-2011-1933?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

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

SQL injection vulnerability in Jifty::DBI before 0.68.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.6% (top 25%)
CISA exploited list	No
Weakness	CWE-89
Published	2019-11-26
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: jifty\

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

Am I affected?

Timeline

2019-11-26 21:15 UTCPublished CVE record published
2026-06-16 23:30 UTCUpdated Record last modified

jifty\ \ UPGRADE

Affected: < 0.68

Fixed in: 0.68

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 0.68 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2011-1933?

\: upgrade to 0.68. Exact commands for each OS are on this page.

Is CVE-2011-1933 being exploited?

CVE-2011-1933 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-2011-1933 affect?

CVE-2011-1933 affects \. Severity is critical (CVSS 9.8). SQL injection vulnerability in Jifty::DBI before 0.68.

How urgent is CVE-2011-1933?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-9390 CRITICAL 9.1 UPGRADE XML::Sig versions before 0.71 for Perl allow XPath injection in ID lookup. verify() and _get_signed_xml() in
CVE-2026-9487 CRITICAL 9.1 UPGRADE XML::Sig versions before 0.71 for Perl allow signature wrapping via duplicate ID. _get_signed_xml() in lib/XM
CVE-2026-18568 HIGH 7.5 UPGRADE XML::Sig versions from 0.29 before 0.72 for Perl allow signature verification bypass because verify returns tr
CVE-2025-40934 CRITICAL 9.3 UPGRADE XML-Sig versions 0.27 through 0.67 for Perl incorrectly validates XML files if signatures are omitted. An att
CVE-2026-42497 HIGH 7.5 UPGRADE Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extracti

References

← Back to latest CVEs