Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-17870: The JBuildozer extension 1.4.1 for Joomla! has SQL Injection via the appid parameter in an entriessearch actio

66
This week
CRITICAL 9.8REMOTEDOWNGRADE

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

The JBuildozer extension 1.4.1 for Joomla! has SQL Injection via the appid parameter in an entriessearch action.

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

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

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.0% (top 13%)
CISA exploited listNo
WeaknessCWE-89
Published2017-12-27
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: jbuildozer

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

jbuildozer jbuildozer DOWNGRADE
Affected: 1.4.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.4.1
1. Check installed version
apt-cache policy jbuildozer || rpm -q jbuildozer || jbuildozer --version
2. No fixed release: DOWNGRADE to a release before 1.4.1 (Debian / Ubuntu)
apt-cache madison jbuildozer sudo apt install jbuildozer=<VERSION_BEFORE_1.4.1> sudo apt-mark hold jbuildozer
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list jbuildozer sudo dnf downgrade jbuildozer-<VERSION_BEFORE_1.4.1> sudo dnf versionlock add jbuildozer
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.

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-2017-17870?

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

Is CVE-2017-17870 being exploited?

CVE-2017-17870 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-2017-17870 affect?

CVE-2017-17870 affects jbuildozer. Severity is critical (CVSS 9.8). The JBuildozer extension 1.4.1 for Joomla! has SQL Injection via the appid parameter in an entriessearch action.

How urgent is CVE-2017-17870?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Joomla vulnerabilities

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.