Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2017-9030

7.5 · HIGH

The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla!

Published May 17, 2017CWE-22EPSS 2.10%

Overview

CVE-2017-9030 is a high-severity vulnerability. It was published on May 17, 2017 and has a CVSS 3.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a directory traversal attack that bypasses a uniqid protection mechanism, and makes it easier to read arbitrary uploaded files.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refnavixia.com/storage/app/media/uploaded-files/CVE/cve-2017-521415.txtRefnavixia.com/storage/app/media/uploaded-files/CVE/cve-2017-521415.txt

How CyberStrike helps

Frequently asked questions

What is CVE-2017-9030?

CVE-2017-9030 is a high-severity vulnerability. It was published on May 17, 2017 and has a CVSS 3.0 base score of 7.5 (HIGH).

How severe is CVE-2017-9030?

This vulnerability has a CVSS 3.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-9030?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-9030?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-9030 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2017

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999