Quick answers
- Is CVE-2019-25751 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-25751 being exploited in the wild.
- How severe is CVE-2019-25751?
- High severity, with a CVSS score of 8.2, published 19 June 2026.
- Which products and versions are affected?
- Cmsjunkie J-ClassifiedsManager 3.0.5 and earlier.
- Is there a fix for CVE-2019-25751?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2019-25751 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2019-25751?
- Check whether you run Cmsjunkie J-ClassifiedsManager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An SQL injection vulnerability exists in the J-ClassifiedsManager component (version 3.0.5 and below) for Joomla. The flaw is located within the 'displayads' component, specifically failing to properly sanitize the 'categorySearch', 'adType', and 'citySearch' POST parameters. An unauthenticated remote attacker can send crafted SQL payloads to these parameters to perform out-of-band or error-based data extraction. This allows for the retrieval of sensitive information from the underlying database, such as database names, version information, and user tables. While the vulnerability was publicly disclosed with a proof-of-concept in 2019, it was formally assigned a CVE in 2026.
Affected products
- CMSJunkie J-ClassifiedsManager 3.0.5 and earlier
Timeline
- 2019-01-23: disclosed: Initial exploit code published on Exploit-DB
- 2026-06-19: advisory: CVE-2019-25751 published by VulnCheck and NVD