CVE-2026-15502
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was detected in AojiaoZero Antaris 1.0. This affects the function _rewardPurchase of the file /ipn.php of the component PayPal IPN Payment Handler. The manipulation of the argument item_number results in sql injection. The attack may be performed from remote. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the PayPal IPN Payment Handler's _rewardPurchase function in /ipn.php. The item_number parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the ipn.php fileSearch the web root directory for the file ipn.php used for PayPal IPN processingAffected if The file exists and is part of the deployed application
-
Verify the _rewardPurchase function existsOpen ipn.php and search for the function definition '_rewardPurchase' or 'function _rewardPurchase'Affected if The function is present in the code
-
Check item_number parameter handlingWithin the _rewardPurchase function, locate where $_POST['item_number'] or $item_number is used in SQL query contextsAffected if The item_number parameter is directly concatenated into SQL queries without escaping, sanitization, or use of prepared statements
-
Inspect SQL query constructionReview all SQL queries in the _rewardPurchase function that include the item_number variable - look for patterns like "SELECT ... WHERE item_number = '$item_number'" or similar string concatenationAffected if Dynamic SQL construction with unsanitized item_number is found (not using parameterized queries or proper escaping)
-
Test parameter behaviorIf possible, send a crafted PayPal IPN request with item_number containing SQL metacharacters (e.g., "' OR '1'='1") and observe if it produces SQL errors or unexpected database behaviorAffected if SQL syntax errors appear in logs or the injected payload influences query logic
-
Review database user privilegesCheck the database user configured in ipn.php - verify if it has more privileges than necessary (e.g., not restricted to specific tables)Affected if Database user has elevated privileges that could allow exploitation impact to be worse
If the ipn.php file contains the _rewardPurchase function and the item_number parameter is used in dynamically built SQL queries without prepared statements or proper sanitization, the environment is vulnerable to CVE-2026-15502.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements for the item_number parameter in the _rewardPurchase function. Validate and sanitize all user inputs before database operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data