Technical impact
The Sadad QA Payment WordPress plugin up to version 1.28 fails to validate the authenticity of payment notifications because the merchant secret key used to compute the signature is empty by default. The verification step therefore accepts any attacker‑controlled signed data, effectively allowing an unauthenticated attacker to craft a payment‑confirmation request that the plugin treats as legitimate. This flaw is a CWE‑345 issue (Improper Verification of Cryptographic Signature). The result is that an attacker can register arbitrary orders as paid without sending a real payment, creating the potential for financial fraud and loss of goods or services.
Affected Systems
The attack impacts any WordPress installation that has installed the Sadad QA Payment plugin version 1.28 or earlier and has left the merchant secret at its default empty value. The issue is vendor‑agnostic beyond the plugin itself, so the affected product is the Sadad QA Payment WordPress plugin from the Unknown vendor. Multiple site instances or hosting environments are therefore susceptible if the plugin has not been updated.
Risk and Exploitability
The CVSS score of 5.3 classifies the vulnerability as medium severity. EPSS information is not available, and the case is not listed in the CISA KEV catalog, indicating that it is not currently known to be exploited. The flaw can be exploited remotely via HTTP requests directed at the plugin’s payment‑confirmation endpoint; no authentication is required. Because the attacker controls the input that is intended to be signed, the attack path is straightforward, making this a low‑effort vulnerability for anyone with network access to the site.