Skip to content

Cross-Site Request Forgery in JFinalCMS via /admin/category/updateStatus

High severity GitHub Reviewed Published Dec 5, 2023 to the GitHub Advisory Database • Updated Dec 12, 2023

Package

maven com.jfinal:jfinal (Maven)

Affected versions

<= 5.0.0

Patched versions

None

Description

JFinalCMS v5.0.0 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/category/updateStatus.

References

Published by the National Vulnerability Database Dec 5, 2023
Published to the GitHub Advisory Database Dec 5, 2023
Reviewed Dec 12, 2023
Last updated Dec 12, 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.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.064%
(30th percentile)

Weaknesses

CVE ID

CVE-2023-49397

GHSA ID

GHSA-5f56-h6fg-rcrh

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.