dbcve.org
CertificateApplication · Greatdevelopers

CVE-2026-2184

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-08
Fix available
A fix is available. Upgrade to after 2017-10-16 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 detected in Great Developers Certificate Generation System up to 97171bb0e5e22e52eacf4e4fa81773e5f3cffb73. This vulnerability affects unknown code of the file /restructured/csv.php. The manipulation of the argument photo results in os command injection. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The code repository of the project has not been active for many years.

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

OS command injection vulnerability in Great Developers Certificate Generation System's /restructured/csv.php file. The 'photo' parameter is not properly sanitized before being used in a system call, allowing remote attackers to execute arbitrary OS commands with the privileges of the web server.

MitigationImplement strict input validation and sanitization for the 'photo' parameter, preferably avoiding shell execution entirely. If shell commands are necessary, use escapeshellarg() or better yet, refactor to use PHP native functions instead of system calls.

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
CertificateApplication
Affected:<= 2017-10-16

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the vulnerable csv.php file
    Search the web root directory for the file at path /restructured/csv.php or use find command: find /var/www -name 'csv.php' -path '*/restructured/*' 2>/dev/null
    Affected if The file /restructured/csv.php exists in the web application directory
  2. Identify the installed version of Greatdevelopers Certificate
    Check for version files such as VERSION, changelog, or composer.json in the application root, or inspect headers/comments in the csv.php file for date/version strings
    Affected if The version date is 2017-10-16 or earlier, or no version information is found but the application is this specific product
  3. Verify the vulnerable parameter handling exists
    Inspect the csv.php file for code that uses the 'photo' parameter in system calls (shell_exec, exec, passthru, system, or backtick operators) without proper sanitization using escapeshellarg or similar
    Affected if The csv.php file contains a system call that incorporates the 'photo' parameter directly without input validation
  4. Confirm the web server can execute commands
    Check if the web server user (www-data, apache, nginx) has execute permissions and if PHP system functions are not disabled in php.ini (check disable_functions directive)
    Affected if PHP system functions are enabled and the web server user has execution permissions on the host system
  5. Determine if the endpoint is exposed
    Verify the /restructured/ directory is accessible via the web server and the csv.php can be reached via HTTP/HTTPS request
    Affected if The csv.php file is accessible over the network through the web server

The environment is affected if the Greatdevelopers Certificate application is installed with version dated 2017-10-16 or earlier, the /restructured/csv.php file exists, and it contains unsanitized 'photo' parameter usage in system calls accessible via the web.

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 2017-10-16
Interim mitigation

Implement strict input validation and sanitization for the 'photo' parameter, preferably avoiding shell execution entirely. If shell commands are necessary, use escapeshellarg() or better yet, refactor to use PHP native functions instead of system calls.

Recommended fix Moderate confidence
  1. 1. Identify all instances of the affected application (Great Developers Certificate Generation System) in your environment.
  2. 2. Locate the file /restructured/csv.php in the application codebase.
  3. 3. Since the project repository is abandoned with no active development, there is no official patch or fixed release available.
  4. 4. Remove or delete the /restructured/csv.php file if it is not required for business functionality.
  5. 5. If the file is required, implement input validation and sanitization on the 'photo' parameter to prevent command injection - validate that the input contains only expected characters (e.g., alphanumeric, safe file extensions) and does not contain shell metacharacters like ; | & $ ` or newlines.
  6. 6. Apply web server configuration (e.g., .htaccess, nginx/Apache directives) to restrict execution of system commands from web-facing scripts.
  7. 7. Consider deploying a Web Application Firewall (WAF) rule to detect and block command injection attempts.
  8. 8. If the application is no longer actively maintained, plan to replace it with an actively supported certificate generation solution.
Caveat No upgrade path available - the project is abandoned with no active repository

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

Fix this in Certificate Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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