How severe is CVE-2025-10930?

No CVSS score has been assigned to CVE-2025-10930 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-10930?

CVE-2025-10930 affects the following packages: drupal/currency (Packagist:https://packages.drupal.org/8). Ecosystems affected: Packagist:https://packages.drupal.org/8.

How do I fix CVE-2025-10930?

Update drupal/currency to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10930 is resolved across your whole dependency graph.

How do I detect CVE-2025-10930 in my Packagist:https://packages.drupal.org/8 dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/currency, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-10930 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-10930 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-10930 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-10930?

CVE-2025-10930 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-10930?

CVE-2025-10930 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-10930 published, and has it been updated?

CVE-2025-10930 was published on September 24, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Packagist:https://packages.drupal.org/8

Not in CISA KEV

CVE-2025-10930 — currency

CVE-2025-10930 is a Cross-Site Request Forgery (CSRF) vulnerability in drupal/currency. A fix is available for drupal/currency — see the affected versions and patch details below.

Also known asGHSA-27fv-rpgj-4c6m

Published

Sep 24, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-10930.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦drupal/currency

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist:https://packages.drupal.org/8 packages — download data is not available via public APIs for these ecosystems.

Description

This module allows you to use different currencies on your website and do currency conversion.

The module doesn't sufficiently protect routes used to enable and disable currencies from Cross-Site Request Forgery (CSRF) attacks, potentially allowing an attacker to trick an admin into changing settings.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Packagist:https://packages.drupal.org/8	`drupal/currency`	all versions	3.5.0

Affected Products

1 product · 1 configurations

Application

currency2bits

< 8.x-3.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/currency, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/currency to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10930 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

This module allows you to use different currencies on your website and do currency conversion. The module doesn't sufficiently protect routes used to enable and disable currencies from Cross-Site Request Forgery (CSRF) attacks, potentially allowing an attacker to trick an admin into changing settings.

O3 Security · Impact-Aware SCA

Is CVE-2025-10930 in your dependencies?

Find it across Packagist:https://packages.drupal.org/8, including transitive dependencies.

Scan my dependencies How O3 SCA works