thejshen contentManagementSystem 1.04 GET Parameter ID sql injection

Summaryinfo

A vulnerability marked as critical has been reported in thejshen contentManagementSystem 1.04. This issue affects some unknown processing of the component GET Parameter Handler. Performing a manipulation of the argument ID results in sql injection. This vulnerability was named CVE-2019-25303. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in thejshen contentManagementSystem 1.04. It has been classified as critical. This affects an unknown code of the component GET Parameter Handler. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

TheJshen ContentManagementSystem 1.04 contains a SQL injection vulnerability that allows attackers to manipulate database queries through the 'id' GET parameter. Attackers can exploit boolean-based, time-based, and UNION-based SQL injection techniques to extract or manipulate database information by crafting malicious query payloads.

The weakness was presented by Cakes as 47569. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2019-25303 since 02/06/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (47569) and EUVD (EUVD-2019-19403). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• thejshen

Name

• contentManagementSystem

Version

• 1.04

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion