CVE-2025-34336
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 · uneditedeGovFramework/egovframe-common-components versions up to and including 4.3.1 contain an unauthenticated file upload vulnerability via the /utl/wed/insertImage.do and /utl/wed/insertImageCk.do image upload endpoints. These controllers accept multipart requests without authentication, pass the uploaded content to a shared upload helper, and store the file on the server under a framework-controlled path. The framework then returns a download URL that can be used to retrieve the uploaded content, including an attacker-controlled Content-Type within the limits of the image upload functionality. While a filename extension whitelist is enforced, the attacker fully controls the file contents. The response MIME type used is also attacker-controlled when the file is served up to version < 4.1.2. Since version 4.1.2, it is possible to download any image uploaded with any whitelisted content type. But any file uploaded other than an image will be served with the `application/octet-stream` content type (the content type is no longer controlled by the attacker since version 4.1.2). This enables an unauthenticated attacker to use any affected application as a persistent file hosting service for arbitrary content under the application's origin. KISA/KrCERT has identified this unpatched vulnerability as "KVE-2023-5280."
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 confidenceeGovFramework/egovframe-common-components versions up to 4.3.1 contain unauthenticated file upload vulnerabilities in /utl/wed/insertImage.do and /utl/wed/insertImageCk.do endpoints. These controllers accept multipart requests without authentication, allowing attackers to upload arbitrary file content (though with whitelisted extensions). The framework returns a download URL, enabling the affected application to serve as a persistent file hosting service under the application's origin.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/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 the application uses eGovFrameworkSearch the application codebase, build files (pom.xml, build.gradle), or runtime classpath for 'egovframe-common-components' or 'eGovFramework' libraries. Check WAR/EAR manifests or dependency lists.Affected if The application includes egovframe-common-components in its dependencies
-
Determine the installed version of egovframe-common-componentsLocate the version from the build configuration file (e.g., pom.xml dependency declaration, gradle dependencies), or inspect the included JAR file name and manifest. Compare to the affected range: versions up to and including 4.3.1.Affected if The version is 4.3.1 or lower
-
Verify the vulnerable endpoints are accessibleAttempt to access (or inspect application routing/configuration for) the endpoints /utl/wed/insertImage.do and /utl/wed/insertImageCk.do. Check the application's URL patterns and controller mappings for these paths.Affected if These upload endpoints exist and respond to requests
-
Confirm upload endpoints lack authenticationReview the security configuration (e.g., Spring Security XML/Java config, filter chains) for permitAll rules or missing security constraints on /utl/wed/insertImage.do and /utl/wed/insertImageCk.do. Attempt an unauthenticated multipart request to these endpoints.Affected if The endpoints are accessible without authentication credentials or session cookies
-
Check if file upload feature is enabledInspect the Spring servlet configuration (multipart-config) and the controller implementation to verify the upload functionality is active and not disabled or blocked by other means.Affected if The multipart file upload handler is configured and functional for these endpoints
If the application uses egovframe-common-components version 4.3.1 or lower and exposes /utl/wed/insertImage.do or /utl/wed/insertImageCk.do without authentication, the environment is vulnerable to unauthenticated file upload.
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 dataAdd authentication and authorization checks to the vulnerable upload endpoints; implement proper server-side content-type validation beyond extension checking; consider restricting upload functionality to authenticated users only.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34336 — 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-34336 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