dbcve.org
Connect CmsApplication · Opensource Workshop

CVE-2026-32299

HIGH · 7.5 CVSS v3.1 Published 2026-03-23
Fix available
A fix is available. Upgrade to 1.41.1 / 2.41.1 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
Connect-CMS is a content management system. In versions on the 1.x series up to and including 1.41.0 and versions on the 2.x series up to and including 2.41.0, an improper authorization issue in the page content retrieval feature may allow retrieval of non-public information. Versions 1.41.1 and 2.41.1 contain a patch.

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

Connect-CMS versions 1.x through 1.41.0 and 2.x through 2.41.0 contain an improper authorization vulnerability in the page content retrieval feature. This broken access control issue allows unauthenticated or unauthorized users to access non-public information by exploiting the authorization logic in the page content retrieval endpoint.

MitigationUpgrade Connect-CMS to version 1.41.1 or 2.41.1 (whichever series is applicable) to apply the authorization fix. Verify that page content retrieval correctly enforces access controls for non-public pages after upgrading.

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
Connect CmsApplication
Affected:>= 1.0.0, < 1.41.1>= 2.0.0, < 2.41.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify the installed Connect-CMS version
    Locate the version file or check the admin dashboard for the current Connect-CMS version number (typically found in a version.php file, composer.json, or the admin 'System' or 'About' section)
    Affected if The installed version is 1.x through 1.41.0 or 2.x through 2.41.0 (any version below 1.41.1 or 2.41.1)
  2. Verify the page content retrieval feature exists
    Check if the application's page content retrieval endpoint is accessible by examining the routes or controller handling page content requests (often routed under /page/ or /content/ paths in the web application)
    Affected if The page content retrieval endpoint exists and is routable in the application
  3. Confirm presence of non-public pages
    Review the CMS for any pages marked as private, draft, members-only, or otherwise restricted from public access using the admin interface or database
    Affected if The application contains pages with access restrictions (private, members-only, or restricted content)
  4. Test access to restricted page content
    Attempt to access a known restricted page via the content retrieval endpoint without authentication or with a low-privilege account to see if content is returned
    Affected if Content from restricted pages is returned without proper authorization checks

A user is affected if Connect-CMS version is below 1.41.1 or 2.41.1 and the page content retrieval feature is accessible to unauthenticated or unauthorized users.

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.41.1 / 2.41.1 or later
Fixed in 1.41.12.41.1
Interim mitigation

Upgrade Connect-CMS to version 1.41.1 or 2.41.1 (whichever series is applicable) to apply the authorization fix. Verify that page content retrieval correctly enforces access controls for non-public pages after upgrading.

Recommended fix High confidence

Upgrade to Connect CMS 1.41.1 (for 1.x series) or 2.41.1 (for 2.x series)

  1. 1. Backup your Connect CMS database and files before upgrading.
  2. 2. Review the Connect CMS release notes for versions 1.41.1 and 2.41.1 to understand changes.
  3. 3. If running the 1.x series, upgrade to version 1.41.1. If running the 2.x series, upgrade to version 2.41.1.
  4. 4. Use your package manager or follow the standard upgrade process for Connect CMS (e.g., Composer update or git pull).
  5. 5. Clear any caches after upgrading.
  6. 6. Verify that the page content retrieval feature now properly enforces authorization checks.

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

Fix this in Connect Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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