CVE-2026-2183 — Greatdevelopers Certificate Generation System Unrestricted File Upload (CVE-2026-2183)
A security vulnerability has been detected in Great Developers Certificate Generation System up to 97171bb0e5e22e52eacf4e4fa81773e5f3cffb73. This affects an unknown part of the file /restructured/csv.php. The manipulation leads to unrestricted upload. Remote exploitation of the attack is possible. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The code repository of the project has not been active for many years.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+2
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Greatdevelopers Certificate, Greatdevelopers Certificate Generation System).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Greatdevelopers | Certificate | ≤ 2017-10-16 | Vulnerable | NIST National Vulnerability Database |
| Greatdevelopers | Certificate Generation System | version 97171bb0e5e22e52eacf4e4fa81773e5f3cffb73 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.3 | CVSS 4.0 | Medium | — | — | cna@vuldb.com via NIST National Vulnerability Database |
| 5.3 | CVSS 4.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 6.3 | CVSS 3.1 | Medium | 2.8 | 3.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 6.3 | CVSS 3.1 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 6.3 | CVSS 3.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
| 6.5 | CVSS 2.0 | Medium | 8.0 | 6.4 | cna@vuldb.com via NIST National Vulnerability Database |
| 6.5 | CVSS 2.0 | Medium | — | — | VulDB via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.25%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Analysis and videos
CVE-2026-2183: Greatdevelopers Certificate Generation System Unrestricted File Upload
A vulnerability classified as unrestricted upload of a file with dangerous type (CWE-434) was reported in the Great Developers Certificate Generation System, in an unspecified part of /restructured/csv.php. The NVD record assigns a CVSS 3.1 base score of 9.8 (critical) and describes remote exploitation as possible. No confirmed exploitation appears in the sources consulted, and no fixed version is listed.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · great developers/certificate generation system
- SSVC assessment updated
- Record published
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-2184 Great Developers Certificate Generation System OS Command Injection via photo Parameter Feb 8, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-2183 is "Greatdevelopers Certificate Generation System Unrestricted File Upload (CVE-2026-2183)", rated Critical. It affects Certificate (Greatdevelopers); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.