CVE-2025-4430
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 · uneditedUnauthorized access to "/api/Token/gettoken" endpoint in EZD RP allows file manipulation.This issue affects EZD RP in versions before 20.19 (published on 22nd August 2024).
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 confidenceThe EZD RP application contains an authentication/authorization bypass vulnerability in the /api/Token/gettoken endpoint that allows unauthenticated attackers to manipulate files on the system.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify if EZD RP is installedSearch for EZD RP in installed programs (Windows: Add/Remove Programs, Linux: check common application directories or package managers)Affected if EZD RP software is found on the system
-
Determine the installed EZD RP versionCheck the application version through its GUI (usually in Help > About), configuration files, or installation directory metadataAffected if Version is below 20.19 (e.g., 20.18, 20.17, older)
-
Check if the /api/Token/gettoken endpoint is accessibleAttempt to access http(s)://<server>/api/Token/gettoken or review web server access logs for requests to this endpointAffected if Endpoint returns a response (even an error) indicating it is reachable
-
Verify the authentication bypass conditionSend a request to the /api/Token/gettoken endpoint without valid credentials and observe if it returns a token or accepts the request without rejectionAffected if Endpoint issues a token or allows file operations without authentication
-
Check for unauthorized file modificationsReview application logs, file system timestamps in directories the application accesses, or web server logs for suspicious file write operationsAffected if Files were modified via the application without proper authentication records
You are affected if EZD RP version is installed and is below 20.19, and the /api/Token/gettoken endpoint is exposed and can be accessed without credentials to perform file operations.
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.
dbcve · scopedUpgrade EZD RP to version 20.19 or later to remediate this vulnerability.
EZD RP version 20.19 (published 22nd August 2024)
- Check current installed version of EZD RP to confirm it is before 20.19
- Review release notes and changelog for version 20.19 to understand changes and any prerequisites
- Plan and schedule the upgrade during a maintenance window
- Backup current EZD RP installation, configuration, and database
- Upgrade EZD RP to version 20.19 or later following vendor documentation
- Verify the /api/Token/gettoken endpoint now properly requires authorization
- Test that unauthorized file manipulation through this endpoint is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4430 — 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-4430 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