VYPR
High severityNVD Advisory· Published Dec 5, 2023· Updated Aug 2, 2024

CVE-2023-49395

CVE-2023-49395

Description

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

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

JFinalCMS v5.0.0 has a CSRF vulnerability in the category update endpoint, allowing unauthorized category modifications via crafted requests.

Vulnerability

Overview

JFinalCMS v5.0.0 is affected by a Cross-Site Request Forgery (CSRF) vulnerability in the /admin/category/update endpoint. The application fails to implement anti-CSRF tokens or other request validation mechanisms, allowing an attacker to craft malicious HTML forms that, when visited by an authenticated administrator, perform unauthorized category modifications without the user's consent [1][2].

Exploitation

Scenario

An attacker can exploit this vulnerability by tricking an authenticated CMS administrator into visiting a malicious web page containing an auto-submitting HTML form. The form includes all necessary parameters (e.g., id, name, parentId) to update a category entry. Since the CMS does not verify the origin of the request, the admin's browser will send a valid session cookie along with the forged POST request, executing the attacker's intended changes [2]. The PoC demonstrates how the form targets http://127.0.0.1:8888/admin/category/update with hidden inputs that mirror legitimate update requests.

Impact

Successful exploitation enables an attacker to modify existing categories, rename them, change associated templates, or alter other configuration fields. This can lead to content defacement, broken site navigation, or further administrative actions if the attacker chains this CSRF with other vulnerabilities. The attack requires no prior authentication on the attacker's part, only that a logged-in admin triggers the malicious request.

Mitigation

At the time of publication, no official patch has been released. Mitigation recommendations include implementing anti-CSRF tokens (e.g., synchronizer tokens), checking the Origin or Referer header, or using SameSite cookies. The vendor has not responded to the report [1][2].

AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
com.jfinal:jfinalMaven
<= 5.0.0

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

3

News mentions

0

No linked articles in our index yet.