dbcve.org
Windu CmsApplication · Windu

CVE-2025-59111

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 →
71/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
Windu CMS is vulnerable to Broken Access Control in user editing functionality. Malicious attacker can send a GET request which allows privileged users to delete Super Admins which is not possible with GUI. 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 v4.1 contains a Broken Access Control vulnerability in its user editing functionality. Attackers can send a crafted GET request to delete Super Admin accounts, an action that is not permitted through the application's GUI. This bypasses normal authorization checks and allows privilege escalation.

MitigationUpgrade Windu CMS to version 4.1 build 2250 or later, which contains the security fix for this access control bypass.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

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
    Look for the Windu CMS directory structure, typically in the web root. Check for the presence of index.php and the /public folder characteristic of Windu installations.
    Affected if Windu CMS is installed on the server.
  2. Determine Windu CMS version
    Locate the version file or check the main index.php for a version constant. Common locations include a /data/version.php file or the main class definition.
    Affected if The installed version is exactly 4.1.
  3. Check build number
    Inspect the version file or class for a build number. Look for a build, revision, or buildNumber variable alongside the version string.
    Affected if The build number is below 2250, indicating an unpatched version.
  4. Verify user editing endpoint accessibility
    Review web server access logs for GET requests to user management endpoints such as /admin/user/delete or /user/delete. Check for unusual patterns involving user ID parameters.
    Affected if GET requests to user deletion endpoints are being processed (not rejected) by the application.
  5. Audit Super Admin accounts
    Query the users table in the database to enumerate accounts with Super Admin privileges. Check for any unexpected accounts or unauthorized modifications.
    Affected if Super Admin accounts exist and the application allows unauthenticated or low-privilege access to deletion functions.

You are affected if Windu CMS version 4.1 with a build number below 2250 is installed and the application processes deletion requests to user management endpoints without proper authorization checks.

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 contains the security fix for this access control bypass.

Recommended fix High confidence

Windu CMS 4.1 build 2250

  1. Upgrade Windu CMS from version 4.1 to version 4.1 build 2250
  2. After upgrading, verify the build number matches 2250 in the system information or admin panel
  3. Test that the user editing functionality now properly enforces authorization controls - specifically verify that non-Super Admin users cannot delete Super Admin accounts

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

Fix this in Windu Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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