How severe is CVE-2015-7857?

No CVSS score has been assigned to CVE-2015-7857 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-7857?

Affected package information for CVE-2015-7857 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2015-7857?

No fixed version has been published for CVE-2015-7857 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2015-7857 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2015-7857, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-7857?

CVE-2015-7857 has an EPSS (Exploit Prediction Scoring System) score of 93.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2015-7857?

CVE-2015-7857 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2015-7857?

CVE-2015-7857 affects joomla joomla\! (15 versions, e.g. 3.2.0, 3.2.1, 3.2.2…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2015-7857 published, and has it been updated?

CVE-2015-7857 was published on October 29, 2015 and was last updated on May 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2015-7857

SQL injection vulnerability in the getListQuery function in administrator/components/com_contenthistory/models/history.php in Joomla! 3.2 before 3.4.5 allows remote attackers to execute…

Published

Oct 29, 2015

Updated

May 6, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

93.9%probability of exploitation in next 30 days

Very High Risk100th percentile+21.71%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

SQL injection vulnerability in the getListQuery function in administrator/components/com_contenthistory/models/history.php in Joomla! 3.2 before 3.4.5 allows remote attackers to execute arbitrary SQL commands via the list[select] parameter to index.php.

Affected Products

1 product · 15 configurations

Application

joomla\!joomla

15 versions

3.2.03.2.13.2.23.2.33.2.43.3.03.3.13.3.23.3.33.3.43.4.03.4.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-38797remotephp✓ Verified

Joomla! 3.4.4 Component Content History - SQL Injection / Remote Code Execution (Metasploit)

by Metasploit · Nov 23, 2015

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-7857 in your stack?

O3 detects CVE-2015-7857 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works