Vendor Joomla

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type »

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product »

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation »

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability »

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector »

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication »

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction »

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index »

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base »

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp »

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB »

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD »

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

Vendor »

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research »

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day »

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today »

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume »

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities »

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (6): CMS (300), Clantools (1), Com Cbe (1), Com Jresearch (1), Com Shoutbox (1), D4J eZine (1)

Link to Vendor Website: https://www.joomla.org/

PublishedBaseTempVulnerabilityProdExpRemCTICVE
08/26/20205.24.9Joomla CMS mod_latestactions cross site scriptingContent Management SystemNot DefinedOfficial Fix0.04CVE-2020-24599
08/26/20206.66.3Joomla CMS com_content redirectContent Management SystemNot DefinedOfficial Fix0.04CVE-2020-24598
07/15/20206.36.3Joomla CMS com_installer cross-site request forgeryContent Management SystemNot DefinedNot Defined0.06CVE-2020-15700
07/15/20205.35.3Joomla CMS Validation insufficient verification of data authenticityContent Management SystemNot DefinedNot Defined0.04CVE-2020-15699
07/15/20205.35.3Joomla CMS Filter Credentials information disclosureContent Management SystemNot DefinedNot Defined0.05CVE-2020-15698
07/15/20205.35.3Joomla CMS permission assignmentContent Management SystemNot DefinedNot Defined0.05CVE-2020-15697
07/15/20205.45.4Joomla CMS mod_random_image cross site scriptingContent Management SystemNot DefinedNot Defined0.00CVE-2020-15696
07/15/20206.36.3Joomla CMS com_privacy cross-site request forgeryContent Management SystemNot DefinedNot Defined0.05CVE-2020-15695
06/02/20205.95.6Joomla CMS Textfilter permissionsContent Management SystemNot DefinedOfficial Fix0.06CVE-2020-13763
06/02/20205.24.9Joomla CMS com_modules cross site scriptingContent Management SystemNot DefinedOfficial Fix0.06CVE-2020-13762
06/02/20205.24.9Joomla CMS Articles cross site scriptingContent Management SystemNot DefinedOfficial Fix0.02CVE-2020-13761
06/02/20206.56.2Joomla CMS com_postinstall cross-site request forgeryContent Management SystemNot DefinedOfficial Fix0.03CVE-2020-13760
04/21/20206.36.1Joomla CMS com_users authorizationContent Management SystemNot DefinedOfficial Fix0.05CVE-2020-11891
04/21/20206.36.1Joomla CMS ACL input validationContent Management SystemNot DefinedOfficial Fix0.02CVE-2020-11890
04/21/20205.95.7Joomla CMS com_users authorizationContent Management SystemNot DefinedOfficial Fix0.06CVE-2020-11889
03/16/20208.58.2Joomla CMS sql injectionContent Management SystemNot DefinedOfficial Fix0.00CVE-2020-10243
03/16/20205.24.9Joomla CMS Protostar/Beez3 cross site scriptingContent Management SystemNot DefinedOfficial Fix0.05CVE-2020-10242
03/16/20206.56.2Joomla CMS com_templates cross-site request forgeryContent Management SystemNot DefinedOfficial Fix0.00CVE-2020-10241
03/16/20206.36.1Joomla CMS User Table input validationContent Management SystemNot DefinedOfficial Fix0.05CVE-2020-10240
03/16/20207.57.2Joomla CMS com_fields authorizationContent Management SystemNot DefinedOfficial Fix0.00CVE-2020-10239
03/16/20207.47.1Joomla CMS com_templates exposure of resourceContent Management SystemNot DefinedOfficial Fix0.05CVE-2020-10238
01/28/20205.24.9Joomla CMS com_actionlogs cross site scriptingContent Management SystemNot DefinedOfficial Fix0.06CVE-2020-8421
01/28/20206.56.2Joomla CMS com_templates cross-site request forgeryContent Management SystemNot DefinedOfficial Fix0.06CVE-2020-8420
01/28/20206.56.2Joomla CMS Batch Action cross-site request forgeryContent Management SystemNot DefinedOfficial Fix0.06CVE-2020-8419
12/18/20198.58.2Joomla CMS sql injectionContent Management SystemNot DefinedOfficial Fix0.05CVE-2019-19846

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!