CVE-2024-49317
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ZIPANG Point Maker point-maker allows PHP Local File Inclusion.This issue affects Point Maker: from n/a through <= 0.1.4.
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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability in ZIPANG Point Maker (versions <= 0.1.4) allows attackers to include arbitrary PHP files from the local server due to improper control of filenames in include/require statements. This can lead to sensitive file disclosure or remote code execution if an attacker can control or manipulate included file paths.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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.
-
Identify if ZIPANG Point Maker is installedLocate the application by searching for files named 'pointmaker', 'zipang', or related PHP files in the web server document root or application directoriesAffected if The application is found on the system
-
Determine installed versionCheck version information in configuration files, README files, or the main PHP entry point (commonly found in version constants, config files, or metadata files)Affected if Installed version is 0.1.4 or lower
-
Locate PHP files with dynamic file inclusionSearch source code for include, require, include_once, or require_once statements that use variables (e.g., include($var), require($_GET['page']) without sanitization)Affected if Dynamic file inclusion using variables is found in the codebase
-
Verify input reaches inclusion functionsTrace the data flow from request parameters (GET/POST) to the include/require statements identified in step 3Affected if User-controlled input flows directly to include/require without proper validation
-
Test for path traversal in inclusion parametersAttempt to include known files outside the intended directory (e.g., ../../../../etc/passwd) via web request parameters that map to include statementsAffected if The application allows reading files outside the intended directory through inclusion parameters
You are affected if ZIPANG Point Maker version 0.1.4 or lower is installed AND user-supplied input can reach include/require statements without sanitization.
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 dataImplement strict input validation on file inclusion parameters using whitelist approaches or basename()/realpath() functions to prevent path traversal, and disable allow_url_include if not needed.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49317 — 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-49317 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