Skip to content

baserCMS Cross Site Request Forgery vulnerability

High severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated Jul 7, 2023

Package

composer baserproject/basercms (Composer)

Affected versions

<= 3.0.10

Patched versions

3.0.11

Description

Cross-site request forgery (CSRF) vulnerability in baserCMS version 3.0.10 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

References

Published by the National Vulnerability Database May 12, 2017
Published to the GitHub Advisory Database May 17, 2022
Reviewed Jul 7, 2023
Last updated Jul 7, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.236%
(62nd percentile)

Weaknesses

CVE ID

CVE-2016-4878

GHSA ID

GHSA-fg52-rc36-jp43

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.