Security readout for executives and security teams
Plain-English summary
A WordPress payment plugin, Pago por Redsys, can reflect attacker-supplied script back to a user through the Ds_MerchantParameters parameter. An attacker would need to trick someone into clicking a crafted link. Impact is usually session, account, or page-context theft or manipulation, not direct server takeover.
Executive priority
Schedule remediation promptly for affected WordPress commerce sites, especially customer-facing payment flows. This is not described as actively exploited, but reflected XSS can support credential theft, payment-flow abuse, and brand-impacting phishing.
Technical view
CVE-2024-12467 is a reflected XSS issue in Pago por Redsys versions up to and including 1.0.12. The source attributes it to insufficient sanitization and output escaping of Ds_MerchantParameters. CVSS 3.1 is 6.1, network exploitable, unauthenticated, low complexity, with required user interaction and changed scope.
Likely exposure
Exposure is limited to WordPress sites running the grafreak Pago por Redsys plugin at version 1.0.12 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.
Exploitation context
The bundle says exploitation requires user interaction, such as clicking a link. KEV is false, and no provided source states active exploitation. Treat this as phishing-assisted web risk rather than confirmed in-the-wild compromise.
Researcher notes
Evidence points to reflected XSS tied to Ds_MerchantParameters and corrected code references in the 1.0.13 WordPress plugin tree. The provided bundle does not include exploit telemetry, a KEV listing, or broader product impact beyond this plugin.
Mitigation direction
- Update Pago por Redsys beyond 1.0.12 after checking vendor or WordPress plugin guidance.
- If immediate update is not possible, disable the plugin until remediated.
- Prioritize sites where the plugin handles customer payment redirects or logged-in user flows.
- Monitor vendor, Wordfence, and WordPress plugin sources for current fixed-version guidance.
Validation and detection
- Inventory WordPress installations for the Pago por Redsys plugin and installed version.
- Confirm whether any instance is running version 1.0.12 or earlier.
- Review payment and callback pages for reflected Ds_MerchantParameters handling.
- Check web logs for unusual requests containing Ds_MerchantParameters.
- Verify remediation by confirming deployment of a non-affected plugin version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-12467 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ed05cd81-ca21-41de-9b02-bd84498cd74e?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/pago-redsys-tpv-grafreak/tags/1.0.13/public/partials/pago-redsys-grafreak-public-display.php#L82CVE reference
- https://plugins.trac.wordpress.org/browser/pago-redsys-tpv-grafreak/tags/1.0.13/includes/class-redsysapi.php#L263CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3215878%40pago-redsys-tpv-grafreak&new=3215878%40pago-redsys-tpv-grafreak&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
