dbcve.org
ZkeacmsApplication · Zkea

CVE-2025-10764

HIGH · 8.8 CVSS v3.1 Published 2025-09-21
Fix available
A fix is available. Upgrade to after 4.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A vulnerability was identified in SeriaWei ZKEACMS up to 4.3. This affects the function Edit of the file src/ZKEACMS.EventAction/Controllers/PendingTaskController.cs of the component Event Action System. Such manipulation of the argument Data leads to server-side request forgery. The attack may be performed from remote. The exploit is publicly available and might 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 · high confidence

This is a server-side request forgery (SSRF) vulnerability in SeriaWei ZKEACMS up to version 4.3. The Edit function in PendingTaskController.cs within the Event Action System does not properly validate the Data parameter, allowing remote attackers to manipulate the server into making arbitrary HTTP requests to internal or external resources.

MitigationSince the vendor did not respond to disclosure, no official patch exists. Implement input validation whitelisting for the Data parameter in PendingTaskController.cs to restrict URLs to expected domains, or deploy a WAF rule to block SSRF attack patterns. Consider network segmentation to limit server outbound capabilities.

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
ZkeacmsApplication
Affected:<= 4.3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Check ZKEACMS installed version
    Locate the version number in the application's web.config, appsettings.json, or assembly metadata (dll file properties). Common paths: /wwwroot/, /bin/, or the root application directory.
    Affected if The version is 4.3 or any version lower than 4.3 (the vulnerable version range is <= 4.3).
  2. Verify PendingTaskController.cs exists
    Search the application source code or deployed files for the file PendingTaskController.cs, typically located in the Controllers folder under the Event Action System area.
    Affected if The file exists, indicating the vulnerable component is present in the deployment.
  3. Inspect the Edit action method for Data parameter validation
    Open PendingTaskController.cs and locate the Edit action method. Examine whether the Data parameter undergoes URL validation or sanitization before being used in HTTP requests.
    Affected if The Data parameter is used directly in HTTP requests without proper validation, allowing arbitrary URL manipulation.
  4. Confirm Event Action System module is enabled
    Check if the Event Action System feature is enabled in the CMS administration panel or configuration settings.
    Affected if The Event Action System is active and the Edit function is accessible to users, enabling the attack surface.

You are affected if your ZKEACMS version is 4.3 or lower and the Event Action System with its Edit function in PendingTaskController.cs is accessible without URL validation on the Data parameter.

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 a release after 4.3
Interim mitigation

Since the vendor did not respond to disclosure, no official patch exists. Implement input validation whitelisting for the Data parameter in PendingTaskController.cs to restrict URLs to expected domains, or deploy a WAF rule to block SSRF attack patterns. Consider network segmentation to limit server outbound capabilities.

Recommended fix Moderate confidence

ZKEACMS 4.4 or latest stable release

  1. Check the current ZKEACMS version by reviewing the project files or application startup information
  2. Locate the ZKEACMS project in your solution (typically in src/ZKEACMS.EventAction or similar)
  3. Review the PendingTaskController.cs file in the ZKEACMS.EventAction/Controllers directory
  4. Identify the Edit action method and the Data parameter handling
  5. Upgrade to the latest stable release of ZKEACMS (version 4.4 or later, since 4.3 is the last known vulnerable version)
  6. After upgrading, verify the fix by reviewing the updated PendingTaskController.cs code to ensure the Data parameter is now properly validated
  7. Test the Event Action System functionality to confirm the SSRF vulnerability is mitigated
  8. Deploy the updated version to production
Caveat Review release notes for any breaking changes between 4.3 and the target upgrade version before deploying to production

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

Fix this in Zkeacms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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