Jeequan Jeepay up to 3.2.9 Payment Channel Configuration MchPayInterfaceConfigController saveOrUpdate infoId authorization

Summaryinfo

A vulnerability was found in Jeequan Jeepay up to 3.2.9. It has been declared as problematic. This impacts the function saveOrUpdate of the file MchPayInterfaceConfigController of the component Payment Channel Configuration. Such manipulation of the argument infoId leads to authorization. This vulnerability is traded as CVE-2026-111607. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Jeequan Jeepay up to 3.2.9. Affected by this issue is the function saveOrUpdate of the file MchPayInterfaceConfigController of the component Payment Channel Configuration. The manipulation of the argument infoId with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is integrity, and availability. CVE summarizes:

Jeepay through 3.2.9 contains an insecure direct object reference vulnerability that allows authenticated merchant users to overwrite another merchant application's payment channel configuration by supplying a victim infoId to MchPayInterfaceConfigController.saveOrUpdate. Attackers holding the default ENT_MCH_PAY_CONFIG_ADD permission can replace signing keys, certificates, and fee rates to break or redirect the victim merchant's payment processing.

The advisory is shared for download at hackmd.io. This vulnerability is handled as CVE-2026-111607 since 10/16/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/16/2026).

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Jeequan

Name

• Jeepay

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion