dbcve.org
Windu CmsApplication · Windu

CVE-2025-59110

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Windu CMS is vulnerable to Cross-Site Request Forgery in user editing functionality. Implemented CSRF protection mechanism can be bypassed by using CSRF token of other user. It is worth noting that the registration is open and anyone can create an account. Only version 4.1 was tested and confirmed as vulnerable. This issue was fixed in version 4.1 build 2250.

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

Windu CMS contains a CSRF protection bypass vulnerability where the anti-CSRF token mechanism can be circumvented by using a CSRF token from another user. An attacker with an account (registration is open) can exploit this to forge requests that modify other users' profiles via the user editing functionality.

MitigationUpgrade Windu CMS to version 4.1 build 2250 or later which implements proper CSRF token validation tied to the specific user session.

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
Windu CmsApplication
Affected:= 4.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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify Windu CMS installation and version
    Locate the CMS installation directory and check the version file or header. Common paths include the main index.php or a version/config file in the root directory. Look for version identifier '4.1'.
    Affected if The installed version is exactly 4.1 (without the build 2250 or later fix)
  2. Confirm user registration is open
    Access the registration page (typically /register or /user/register) and verify if new user accounts can be created without admin approval or invitation.
    Affected if User registration is enabled, allowing an attacker to obtain a valid account
  3. Inspect CSRF token validation in user profile editing
    Locate the user editing controller/module (typically in the 'user' or 'users' plugin directory). Examine the code that handles the profile update form submission and check how the CSRF token is validated - whether it validates against the current user's session or accepts any valid token.
    Affected if The CSRF token validation accepts tokens from other user sessions rather than requiring a token bound to the current user's session
  4. Verify build version if available
    Check for a build number in the CMS (often in footer, about page, or version file). Compare against build 2250.
    Affected if Build number is below 2250, indicating the patch is not applied

You are affected if Windu CMS version 4.1 is installed with user registration enabled and the build is below 2250, allowing cross-user CSRF token reuse in the profile editing feature.

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 Windu CMS to version 4.1 build 2250 or later which implements proper CSRF token validation tied to the specific user session.

Recommended fix High confidence

Windu CMS 4.1 build 2250

  1. Backup the current Windu CMS installation including database and files
  2. Download Windu CMS version 4.1 build 2250 from the official source (windu.org)
  3. Replace the existing installation files with the new version, preserving configuration and custom files
  4. Run any provided database migration scripts included in the update
  5. Clear any application caches if applicable
  6. Verify the CSRF protection is functioning correctly in the user editing functionality
  7. Test user account creation and editing to confirm the vulnerability is remediated

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

Fix this in Windu Cms Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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