AojiaoZero Antaris 1.0 PayPal IPN Payment /ipn.php _rewardPurchase item_number sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 1.12 |
Summary
A vulnerability was found in AojiaoZero Antaris 1.0. It has been classified as critical. This vulnerability affects the function _rewardPurchase of the file /ipn.php of the component PayPal IPN Payment Handler. This manipulation of the argument item_number causes sql injection.
The identification of this vulnerability is CVE-2026-15502. It is possible to initiate the attack remotely. There is no exploit available.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in AojiaoZero Antaris 1.0. It has been declared as critical. Affected by this vulnerability is the function _rewardPurchase of the file /ipn.php of the component PayPal IPN Payment Handler. The manipulation of the argument item_number with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
This vulnerability is known as CVE-2026-15502. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/11/2026). MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vendor was contacted early about this disclosure but did not respond in any way. By approaching the search of inurl:ipn.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/11/2026 Advisory disclosed07/11/2026 VulDB entry created
07/11/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2026-15502 (🔒)
GCVE (CVE): GCVE-0-2026-15502
GCVE (VulDB): GCVE-100-377809
Entry
Created: 07/11/2026 14:54Changes: 07/11/2026 14:54 (55)
Complete: 🔍
Submitter: Dest1ny_2
Cache ID: 216::103
Submit
Accepted
- Submit #844725: AojiaoZero Antaris latest (2026-06, no formal release) SQL Injection (by Dest1ny_2)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.