dbcve.org
Eca\Application · Drupal

CVE-2025-3131

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 1.1.12 / 2.0.16 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Drupal ECA: Event - Condition - Action allows Cross Site Request Forgery.This issue affects ECA: Event - Condition - Action: from 0.0.0 before 1.1.12, from 2.0.0 before 2.0.16, from 2.1.0 before 2.1.7, from 0.0.0 before 1.2.*.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Drupal ECA (Event - Condition - Action) module allows attackers to trick authenticated users into executing unintended actions within the ECA workflow engine. This is a standard CSRF attack vector where malicious requests can be forged on behalf of an authenticated administrator.

MitigationUpdate the ECA module to version 1.1.12, 2.0.16, 2.1.7, or 1.2.x (or later) depending on the installed branch to obtain the CSRF token protection fixes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Eca\Application
Affected:< 1.1.12>= 2.0.0, < 2.0.16>= 2.1.0, < 2.1.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the ECA module installation
    Check your Drupal installation for the ECA module directory (commonly in modules/contrib/eca or modules/custom/eca) or query the Drupal system table: SELECT name, filename FROM system WHERE name LIKE '%eca%' AND type = 'module';
    Affected if ECA module is not found in the Drupal installation
  2. Determine installed ECA version
    Check the module's info.yml file (eca.info.yml) in the ECA module directory for the 'version:' field, or run: drush pm:list --filter=eca, or check composer.json in the ECA module folder for the version entry.
    Affected if Unable to determine the version from module metadata
  3. Compare version against vulnerable ranges
    Check if the installed version falls into any of these ranges: < 1.1.12, >= 2.0.0 AND < 2.0.16, >= 2.1.0 AND < 2.1.7. Version 1.2.x and later releases are not affected.
    Affected if Installed version is below 1.1.12, OR between 2.0.0-2.0.15, OR between 2.1.0-2.1.6
  4. Verify ECA module is enabled
    Check if the ECA module is currently enabled for the site: drush state-get system.module_eca or query the 'system' table for status = 1. CSRF only affects authenticated sessions when the module is active.
    Affected if ECA module is installed but currently disabled (not active on the site)

Your environment is affected if the Drupal ECA module is installed, enabled, and its version is 1.1.11 or lower, 2.0.0-2.0.15, or 2.1.0-2.1.6, allowing unauthenticated attackers to trick authenticated administrators into performing unintended ECA workflow actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.12 / 2.0.16 / 2.1.7 or later
Fixed in 1.1.122.0.162.1.7
Interim mitigation

Update the ECA module to version 1.1.12, 2.0.16, 2.1.7, or 1.2.x (or later) depending on the installed branch to obtain the CSRF token protection fixes.

Recommended fix High confidence

1.1.12 (for 1.x users) OR 2.0.16 (for 2.0.x users) OR 2.1.7 (for 2.1.x users)

  1. Identify the currently installed ECA module version from Drupal's admin interface or composer.json
  2. If running a version < 1.1.12 (1.x branch), upgrade to version 1.1.12
  3. If running version >= 2.0.0 and < 2.0.16 (2.0.x branch), upgrade to version 2.0.16
  4. If running version >= 2.1.0 and < 2.1.7 (2.1.x branch), upgrade to version 2.1.7
  5. Upgrade via Composer: composer update drupal/eca --with-all-dependencies OR upload the new version via Drupal's Extend > Install new module interface
  6. Run database updates if prompted: drush updatedb or via Drupal admin
  7. Clear Drupal cache: drush cr or via Drupal admin > Performance > Clear all caches
  8. Verify the upgrade was successful by checking the module version in Drupal's Extend page
Caveat Standard security patch upgrade with no expected breaking changes; always test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eca\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3131 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data