CVE-2025-34336: eGovFramework <= 4.3.1 Unauthenticated File Upload via Web Editor Image Upload Endpoints
eGovFramework/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."
Security readout for executives and security teams
Plain-English summary
An unauthenticated user can upload files through eGovFramework web editor image endpoints and have them served from the affected application’s origin. This can turn a trusted public site into persistent attacker-controlled file hosting. The sources do not show KEV listing or confirmed active exploitation.
Executive priority
Treat as a prompt exposure review for public eGovFrame sites. Business risk is trust abuse and hosted malicious content under your domain, not confirmed server takeover from the provided evidence.
Technical view
eGovFramework/egovframe-common-components through 4.3.1 expose unauthenticated multipart upload handling at /utl/wed/insertImage.do and /utl/wed/insertImageCk.do. Uploaded content is stored and returned via a download URL. Extension filtering exists, but contents are attacker-controlled; older versions also allowed attacker-controlled served MIME type.
Likely exposure
Public-facing applications using egovframe-common-components version 4.3.1 or earlier are most exposed, especially if the web editor image upload routes are reachable without authentication.
Exploitation context
The bundle cites public technical descriptions and third-party advisories, but KEV is false. KISA/KrCERT reportedly tracks it as KVE-2023-5280 and identifies it as unpatched. Evidence of active exploitation is not provided.
Researcher notes
Do not assume arbitrary code execution from the provided bundle. The stated impact is unauthenticated persistent file hosting under application origin, with MIME handling risk varying by version before and after 4.1.2.
Mitigation direction
Check eGovFramework and KISA/KrCERT guidance for a fixed release or official workaround.
Require authentication before access to both web editor image upload endpoints.
Block public access to unused /utl/wed/ image upload routes.
Serve uploaded content from isolated storage or a separate non-trusted origin.
Review and remove unexpected uploaded files from affected storage paths.
Validation and detection
Inventory applications using egovframe-common-components 4.3.1 or earlier.
Check whether /utl/wed/insertImage.do is reachable without login.
Check whether /utl/wed/insertImageCk.do is reachable without login.
Confirm upload handling validates file type by content, not only extension.
Review logs for unauthenticated multipart requests to the affected routes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.