dbcve.org
DrupalCMS

CVE-2022-25273

HIGH · 7.5 CVSS v3.1 Published 2023-04-26
Fix available
A fix is available. Upgrade to 9.2.18 / 9.3.12 or later.
See remediation →
84/100
Remediation priority · High
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
Drupal core's form API has a vulnerability where certain contributed or custom modules' forms may be vulnerable to improper input validation. This could allow an attacker to inject disallowed values or overwrite data. Affected forms are uncommon, but in certain cases an attacker could alter critical or sensitive data.

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 core's form API contains an improper input validation vulnerability that affects certain custom or contributed module forms. Attackers can potentially inject disallowed values or overwrite data through these vulnerable forms. While affected forms are described as uncommon, the vulnerability could allow alteration of critical or sensitive data in certain configurations.

MitigationUpdate Drupal core to the patched version. Review and audit any custom or contributed module forms for proper input validation, as these are the primary targets of this vulnerability.

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
DrupalCMS
Affected:>= 8.0.0, < 9.2.18>= 9.3.0, < 9.3.12

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Determine installed Drupal core version
    Locate the file 'core/lib/Drupal.php' and look for the 'VERSION' constant, or run 'drush status' or 'composer show drupal/core' to retrieve the installed version number.
    Affected if The installed version is >= 8.0.0 and < 9.2.18, or >= 9.3.0 and < 9.3.12
  2. Identify installed custom modules
    Check the 'modules/custom' directory in your Drupal root for any custom-written modules that define forms using the Form API.
    Affected if Any custom modules exist in the modules/custom directory and utilize form submissions
  3. Identify installed contributed modules
    Check the 'modules/contrib' directory or run 'drush pm-list' to list all contributed modules installed from Drupal.org.
    Affected if Any contributed modules are installed that contain custom form implementations
  4. Review form implementations in custom/contributed code
    Search within custom and contributed module directories for files containing 'Form' classes that extend 'FormBase' or 'ConfigFormBase', then inspect the 'buildForm', 'submitForm', or 'validateForm' methods for proper input validation.
    Affected if Any custom or contributed module forms lack proper validation on form element values before processing

You are affected if your Drupal core version is within the vulnerable ranges AND you have custom or contributed modules installed that implement forms without adequate input validation.

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 9.2.18 / 9.3.12 or later
Fixed in 9.2.189.3.12
Interim mitigation

Update Drupal core to the patched version. Review and audit any custom or contributed module forms for proper input validation, as these are the primary targets of this vulnerability.

Recommended fix High confidence

Drupal 9.2.18+ or 9.3.12+ (or migrate from Drupal 8 to Drupal 9)

  1. Review custom and contributed modules for forms that may be affected by improper input validation
  2. Review the Drupal release notes for versions 9.2.18 and 9.3.12 for any additional required updates
  3. Plan and schedule a maintenance window for the upgrade
  4. Back up the entire Drupal site including database and files
  5. Ensure all modules and themes are compatible with the target Drupal version
  6. Upgrade Drupal core to version 9.2.18 or later (if on 9.2.x), or to 9.3.12 or later (if on 9.3.x)
  7. Run database updates via drush updatedb or /update.php
  8. Clear all Drupal caches
Caveat Drupal 8 reached end-of-life in November 2022 - consider migrating to Drupal 9; review module/theme compatibility and test thoroughly before deploying to production

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

Fix this in Drupal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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