🛡️ CVE-2025-28876 — skrill

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: Required — someone has to click, open or visit something.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: None.
• Integrity impact: Low — limited, and the attacker does not choose what is affected.
• Availability impact: None.

Weakness class

CVE-2025-28876 is classified as CWE-352: Cross-Site Request Forgery (CSRF). A state-changing request is accepted without proof it was intended, so another site can trigger it using the victim's session.

Affected software

CVE-2025-28876 is recorded against 1 package.

• skrill (fixed in 1.0.67)

Timeline and source

Published on 11 March 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

patchstack.com

Other advisories for this package

skrill has other advisories on record. If you are patching this one, these are worth checking on the same host:

• MAL-2026-10542 (published 14 Jul 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-352: Cross-Site Request Forgery (CSRF)) in other software:

• CVE-2023-37465 (published 27 Jul 2026)
• CVE-2023-6022 (8.0 High, published 7 Jul 2026)
• CVE-2022-43719 (8.0 High, published 7 Jul 2026)
• CVE-2016-4808 (published 6 Jul 2026)
• CVE-2021-4164 (8.0 High, published 2 Jul 2026)
• CVE-2011-4952 (8.0 High, published 2 Jul 2026)
• CVE-2022-44630 (4.6 Medium, published 11 Jun 2026)
• CVE-2022-47150 (4.3 Medium, published 11 Jun 2026)

Details

Affected Packages

References