LiveActive security incident?Get immediate response
CVE Record

CVE-2024-12467: Pago por Redsys <= 1.0.12 - Reflected Cross-Site Scripting

The Pago por Redsys plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'Ds_MerchantParameters' parameter in all versions up to, and including, 1.0.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-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
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2024-12467Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
grafreakPago por Redsys0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.