dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-39940

MEDIUM · 5.3 CVSS v4.0 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
ChurchCRM is an open-source church management system. Prior to 7.0.0, it was possible in many places across the ChurchCRM application to create a link that, when visited by an authenticated user, would redirect them to any URL chosen by an attacker if they clicked 'Cancel' button on the page. For this write-up the DonatedItemEditor.php will be used as an example, however wherever all instances of 'linkBack' should be assessed. This vulnerability is fixed in 7.0.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 · high confidence

Open redirect vulnerability in ChurchCRM prior to 7.0.0 where the 'linkBack' parameter in multiple pages (including DonatedItemEditor.php) allows authenticated users to be redirected to attacker-controlled URLs when clicking the 'Cancel' button. This is a classic open redirect flaw enabling malicious link crafting.

MitigationUpgrade to ChurchCRM version 7.0.0 or later, which contains the fix. Alternatively, implement strict validation ensuring the 'linkBack' parameter only permits relative/internal URLs.

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

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify installed ChurchCRM version
    Check the version file (typically includes a version.php or similar) in the ChurchCRM installation directory, or access the ChurchCRM admin dashboard and look for the version information under System Settings or About section.
    Affected if The installed version is any version prior to 7.0.0 (e.g., 6.x, 5.x, etc.)
  2. Locate DonatedItemEditor.php file
    Search the web root directory of your ChurchCRM installation for the file DonatedItemEditor.php - typically found in the /src/ or /pages/ directory of the application.
    Affected if The file exists in the installation and the version is below 7.0.0
  3. Inspect linkBack parameter handling in code
    Open DonatedItemEditor.php and search for occurrences of 'linkBack' or 'redirect' to see how the parameter is being processed, specifically looking for how the Cancel button handles the redirect.
    Affected if The code contains unchecked or unvalidated usage of the 'linkBack' parameter for redirection (e.g., no validation that the URL is relative/internal)
  4. Verify authenticated user access to vulnerable page
    Confirm that the DonatedItemEditor.php page is accessible to authenticated users by checking user role permissions or attempting to access the page with valid credentials.
    Affected if Authenticated users can access the DonatedItemEditor.php page and the 'linkBack' parameter influences redirect behavior on the Cancel action

You are affected if your ChurchCRM installation is any version prior to 7.0.0 and the DonatedItemEditor.php file exists with unvalidated 'linkBack' parameter handling.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ChurchCRM version 7.0.0 or later, which contains the fix. Alternatively, implement strict validation ensuring the 'linkBack' parameter only permits relative/internal URLs.

Recommended fix High confidence

7.0.0

  1. Check current ChurchCRM version by reviewing version file or admin dashboard
  2. Backup database and all ChurchCRM files before upgrading
  3. Download ChurchCRM version 7.0.0 or latest stable release from the official repository
  4. Extract and deploy the new version files to the server
  5. Run any database migration scripts included in the 7.0.0 release
  6. Log in to verify the application functions correctly after upgrade
  7. Test that the 'Cancel' button in DonatedItemEditor.php and other pages using 'linkBack' parameter no longer allows arbitrary URL redirection
Caveat Major version upgrades may introduce breaking changes; review release notes for 7.0.0 before upgrading

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

Have this fixed 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 help mitigating

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-2026-39940 — 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-2026-39940 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