dbcve.org
Backdrop CmsApplication · Backdropcms

CVE-2022-34530

MEDIUM · 5.3 CVSS v3.1 Published 2022-08-01
Fix available
A fix is available. Upgrade to after 1.22.0 or later.
See remediation →
62/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
An issue in the login and reset password functionality of Backdrop CMS v1.22.0 allows attackers to enumerate usernames via password reset requests and distinct responses returned based on usernames.

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

Backdrop CMS v1.22.0 contains a user enumeration vulnerability in its password reset functionality. The system returns distinct error messages or behaviors depending on whether a submitted username exists, allowing attackers to harvest valid usernames through repeated password reset requests.

MitigationModify the password reset form to return a generic response message (e.g., 'If an account exists with that email, instructions have been sent') regardless of whether the submitted username or email is valid in the system.

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
Backdrop CmsApplication
Affected:<= 1.22.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check Backdrop CMS installed version
    Locate the version.php file in the Backdrop root directory (usually includes/version.php) and read the $version variable, or check the admin dashboard at /admin/config/system/site-information for the version number
    Affected if Installed version is 1.22.0 or lower
  2. Test password reset with non-existent username
    Navigate to the password reset form (typically at /user/password), enter a username that does NOT exist in the system, and submit the form. Note the exact error message or behavior returned.
    Affected if Response indicates the username does not exist (e.g., 'User X was not found')
  3. Test password reset with existing username
    Navigate to /user/password, enter a username that DOES exist in the system, and submit the form. Note the exact error message or behavior returned.
    Affected if Response indicates the username exists or sends an actual password reset email
  4. Compare password reset responses
    Review both responses from steps 2 and 3. Check if they are different messages or behaviors (e.g., one says user not found, the other shows success message or sends email).
    Affected if The system returns distinct, distinguishable responses that reveal whether a username is valid in the system

If running Backdrop CMS version 1.22.0 or lower AND the password reset form returns different error messages for valid versus invalid usernames, the environment is affected by this user enumeration vulnerability.

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 a release after 1.22.0
Interim mitigation

Modify the password reset form to return a generic response message (e.g., 'If an account exists with that email, instructions have been sent') regardless of whether the submitted username or email is valid in the system.

Recommended fix Moderate confidence

Backdrop CMS 1.23.0 or later

  1. 1. Navigate to the official Backdrop CMS download page or GitHub releases page.
  2. 2. Download the latest stable release of Backdrop CMS (version 1.23.0 or later).
  3. 3. Before upgrading, perform a complete backup of the existing website database and files.
  4. 4. Follow the official Backdrop CMS upgrade instructions to apply the new version.
  5. 5. Verify that the password reset functionality now returns consistent responses regardless of whether the submitted username or email exists.
  6. 6. Test the login and password reset flows to confirm the username enumeration vulnerability is resolved.
Caveat Review the release notes for version 1.23.0 to check for any breaking changes or database updates required for your specific site configuration.

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

Fix this in Backdrop Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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