dbcve.org
Web TDrupal extension · Europa

CVE-2025-3475

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Allocation of Resources Without Limits or Throttling, Incorrect Authorization vulnerability in Drupal WEB-T allows Excessive Allocation, Content Spoofing.This issue affects WEB-T: from 0.0.0 before 1.1.0.

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 · moderate confidence

Drupal WEB-T module versions before 1.1.0 contain two distinct vulnerabilities: an incorrect authorization flaw enabling content spoofing, and a resource allocation issue allowing excessive allocation without proper limits or throttling.

MitigationUpgrade Drupal WEB-T module to version 1.1.0 or later to obtain the vendor patch addressing both the authorization and resource throttling vulnerabilities.

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
Web TDrupal extension
Affected:< 1.1.0

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Confirm Drupal WEB-T module is installed
    Check the Drupal modules directory for the WEB-T module. Typically located at /modules/web_t or /sites/all/modules/web_t, or query the Drupal database: SELECT * FROM system WHERE name = 'web_t' AND type = 'module';
    Affected if The WEB-T module directory or database entry exists in the Drupal installation
  2. Identify the installed version of WEB-T module
    Check the module's .info.yml file (web_t.info.yml) for the version field, or query the Drupal database: SELECT version FROM system WHERE name = 'web_t' AND type = 'module'; Alternatively, check the composer.json file if installed via Composer.
    Affected if The reported version is missing from the .info.yml file or shows a version lower than 1.1.0
  3. Verify the module is enabled
    Query the Drupal database: SELECT status FROM system WHERE name = 'web_t' AND type = 'module'; Status = 1 indicates enabled, Status = 0 indicates disabled.
    Affected if The module status is set to enabled (1)
  4. Check if the module exposes web services or API endpoints
    Inspect the module's routing YAML file (web_t.routing.yml) for publicly accessible routes that may lack proper authorization checks, or review the module's menu links configuration.
    Affected if Publicly accessible routes exist that handle user-supplied content without authorization validation

A defender is affected if the Drupal WEB-T module is installed, enabled, and the installed version is lower than 1.1.0, as both the authorization flaw and resource allocation issue apply to the enabled module.

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.0 or later
Fixed in 1.1.0
Interim mitigation

Upgrade Drupal WEB-T module to version 1.1.0 or later to obtain the vendor patch addressing both the authorization and resource throttling vulnerabilities.

Recommended fix Moderate confidence

1.1.0

  1. Backup your Drupal site database and files before making any changes
  2. Update the WEB-T module to version 1.1.0 or later via your site's module management interface (extend -> WEB-T -> Update)
  3. Alternatively, if using Composer, run: composer update drupal/web_t --with-all-dependencies
  4. Run database updates: drush updatedb (or via admin/reports/status)
  5. Clear all Drupal caches: drush cache-rebuild (or via admin/config/development/performance)
  6. Verify the WEB-T module version shows 1.1.0 or later on the Extend page

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

Fix this in Web T Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3475 — 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-3475 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