Aplazo Payment Gateway
Approved changes feed: RSS · Atom
cpe:2.3:a:aplazopayment:aplazo_payment_gateway:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Aplazopayment (853681f4-98ed-5ff5-94d7-f5d0c363e788) |
|---|---|
| Product | Aplazo Payment Gateway (a682ad68-897d-5df2-bea6-f12c2639c584) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-15512 |
vulnerable | 2026-06-08 07:06:36.329707 |
Aplazo Payment Gateway <= 1.4.3 - Missing Authorization to Unauthenticated Order Status Manipulation
MEDIUM (5.3)
The Aplazo Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the check_success_response() function in all versions up to, and including, 1.4.3. This makes it possible for unauthenticated attackers to set any WooCommerce order to `pending payment` status.
Published: 2026-01-14T06:40:06.342Z
Updated: 2026-04-08T17:10:31.747Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.