Skip to content

Froxlor vulnerable to business logic errors

Low severity GitHub Reviewed Published Aug 11, 2023 to the GitHub Advisory Database • Updated Nov 10, 2023

Package

composer froxlor/froxlor (Composer)

Affected versions

< 2.0.22

Patched versions

2.0.22

Description

Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.22

References

Published by the National Vulnerability Database Aug 11, 2023
Published to the GitHub Advisory Database Aug 11, 2023
Reviewed Aug 11, 2023
Last updated Nov 10, 2023

Severity

Low

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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:H/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.051%
(22nd percentile)

Weaknesses

CVE ID

CVE-2023-4304

GHSA ID

GHSA-9rmf-6qgj-g3wj

Source code

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