CVE-2025-31688Network attack vector

Configuration tampering via tokenless split-state routes

Published Mar 31, 2025 · Updated Apr 29, 2025

CSRF in Drupal Configuration Split before 1.10.0 and 2.0.0 through 2.0.1 allows remote attackers to alter split status via web requests. The enable and disable routes accept state-changing requests without CSRF tokens, allowing a forged request to toggle a named split. Exploitation requires knowledge of the split machine name and deception of a user permitted to modify it; the change affects later exports in both branches and imports in 1.x when configuration overrides do not fix the status.

CVSS severity6.8
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

CSRF in Drupal Configuration Split before 1.10.0 and 2.0.0 through 2.0.1 allows remote attackers to alter split status via web requests. The enable and disable routes accept state-changing requests without CSRF tokens, allowing a forged request to toggle a named split. Exploitation requires knowledge of the split machine name and deception of a user permitted to modify it; the change affects later exports in both branches and imports in 1.x when configuration overrides do not fix the status.

The record

CVE
CVE-2025-31688
Published
Mar 31, 2025
Updated
Apr 29, 2025
Vendor
OAuth.js
Product
Configuration Split
Classifications
CWE-352, CAPEC-62, T1204.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 31, 2025CVE publishedPublication date reported by the CVE source.
  2. Apr 29, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.0.0 <1.10.0
  2. Affected versionversion=2.0.0 <2.0.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

OAuth.js · Configuration Splitversion=0.0.0 <1.10.0; version=2.0.0 <2.0.2

Published CVSS scores

6.8CISA-ADPCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)
CAPEC-62Cross Site Request Forgery
T1204.001User Execution: Malicious Link

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo