CVE-2024-39165
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 · uneditedQR/demoapp/qr_image.php in Asial JpGraph Professional through 4.2.6-pro allows remote attackers to execute arbitrary code via a PHP payload in the data parameter in conjunction with a .php file name in the filename parameter. This occurs because an unnecessary QR/demoapp folder.is shipped with the product.
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 QR/demoapp/qr_image.php file in Asial JpGraph Professional through 4.2.6-pro contains an arbitrary code execution vulnerability. Attackers can achieve remote code execution by supplying a PHP payload in the 'data' parameter along with a .php filename in the 'filename' parameter, likely due to insecure file handling or inclusion. The vulnerability exists because an unnecessary demo application folder ships with the production software.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the QR/demoapp directorySearch the web server document root for the path QR/demoapp/ - common locations include /var/www/html/, /www/, /htdocs/, or the application's vendor directory. Use: find / -type d -name 'demoapp' 2>/dev/null or search within the application folder for 'QR/demoapp'.Affected if The QR/demoapp directory exists in the web-accessible path
-
Verify qr_image.php existsCheck if the file QR/demoapp/qr_image.php is present in the application installation. This is the specific file containing the vulnerability.Affected if The file QR/demoapp/qr_image.php exists on the system
-
Confirm JpGraph versionCheck version file or changelog in the JpGraph installation. Common paths: version.php, changelog.txt, or readme file in the root JpGraph directory. Compare against the affected range: any version through 4.2.6-pro.Affected if Installed version is JpGraph Professional 4.2.6-pro or any earlier version
-
Check if demoapp is web-accessibleVerify the QR/demoapp folder is within the web server's document root or accessible via URL. Attempt to access http://[yourhost]/[path]/QR/demoapp/qr_image.php or check web server configuration for Alias or Directory directives exposing this path.Affected if The demoapp directory is web-accessible (served by the web server)
-
Inspect parameter handling in qr_image.phpIf file access is available, review qr_image.php for 'data' and 'filename' parameters being used in file operations or include/require statements without proper sanitization.Affected if The code accepts and processes unsanitized 'data' and 'filename' parameters
A user is affected if the QR/demoapp directory containing qr_image.php exists and is accessible in their web-facing application, and the JpGraph version is 4.2.6-pro or earlier.
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 dataRemove the entire QR/demoapp folder from production deployments. This demo/sample code should never be present in production environments.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39165 — 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-2024-39165 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