CVE-2025-11272
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 · uneditedA vulnerability has been found in SeriaWei ZKEACMS up to 4.3. This affects the function Delete of the file src/ZKEACMS.Redirection/Controllers/UrlRedirectionController.cs of the component POST Request Handler. The manipulation leads to improper authorization. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceThe ZKEACMS application contains an improper authorization vulnerability in the Delete function of the UrlRedirectionController.cs file. The POST request handler for deleting URL redirections lacks proper authorization checks, allowing remote authenticated users to potentially delete redirection entries without appropriate permissions.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ZKEACMS installationSearch for ZKEACMS DLLs, NuGet packages, or the application bin folder for 'ZKEACMS' assemblies. Check the application's About page or configuration files for ZKEACMS references.Affected if ZKEACMS is not present in the environment, the vulnerability does not apply.
-
Determine ZKEACMS versionLocate the ZKEACMS version number in the project's packages.config, .csproj file, or the assembly version of ZKEACMS.dll in the bin directory. Compare against any official version releases of ZKEACMS.Affected if The installed version is older than versions that contain the fixed UrlRedirectionController.cs with proper authorization.
-
Locate UrlRedirectionController.csFind the UrlRedirectionController.cs file in the source code or decompiled assembly. This file is typically located in the ZKEACMS project under Areas/Admin/Controllers or similar administrative routing paths.Affected if The file does not exist, indicating a different or custom build that may not have this vulnerability.
-
Inspect Delete action for authorizationOpen UrlRedirectionController.cs and examine the Delete method (both POST and any overloads). Look for the presence of [Authorize] attribute or custom authorization logic immediately above the method declaration.Affected if The Delete action lacks an [Authorize] attribute or equivalent role/permission check, meaning any authenticated user can invoke it.
-
Verify URL redirection feature is accessibleLog into the ZKEACMS admin panel and navigate to the URL redirection management section (typically under URL Rewrite or Redirect settings in the CMS admin area). Confirm the feature is available to your user account.Affected if The URL redirection feature is not enabled or accessible in the admin interface, the attack surface does not exist.
The environment is affected if ZKEACMS is installed, the Delete action in UrlRedirectionController.cs lacks proper [Authorize] attributes, and the URL redirection feature is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement proper authorization checks (e.g., [Authorize] attribute with appropriate roles/permissions) on the Delete action in UrlRedirectionController.cs to verify the user has rights to delete URL redirections before processing the request.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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