CVE-2017-5215: The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a rename attack that b

Q: How do I fix CVE-2017-5215?

b2j contact: upgrade to newer than 2.1.12. Exact commands for each OS are on this page.

Q: Is CVE-2017-5215 being exploited?

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

CVE-2017-5215 affects b2j contact. Severity is critical (CVSS 9.8). The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a rename attack that bypasses a "safe file extension" protection mechanism, leading to remote code execution.

Q: How urgent is CVE-2017-5215?

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

This week

CRITICAL 9.8REMOTEUPGRADE

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

The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a rename attack that bypasses a "safe file extension" protection mechanism, leading to remote code execution.

Why this priority

Critical severity
Public exploit reference
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	3.6% (top 11%)
CISA exploited list	No
Weakness	CWE-20
Published	2017-05-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: codextrous

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

Am I affected?

Timeline

2017-05-17 14:29 UTCPublished CVE record published
2026-06-17 01:20 UTCUpdated Record last modified

codextrous b2j contact UPGRADE

Affected: <= 2.1.12

Fixed in: newer than 2.1.12

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 2.1.12 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade b2j-contact

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

b2j contact: upgrade to newer than 2.1.12. Exact commands for each OS are on this page.

Is CVE-2017-5215 being exploited?

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

CVE-2017-5215 affects b2j contact. Severity is critical (CVSS 9.8). The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a rename attack that bypasses a "safe file extension" protection mechanism, leading to remote code execution.

How urgent is CVE-2017-5215?

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

Software pages

Joomla vulnerabilities

Related CVEs

CVE-2017-9030 HIGH 7.5 UPGRADE The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a directory traversal
CVE-2017-5214 HIGH 7.5 UPGRADE The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows prediction of a uniqid

References

← Back to latest CVEs