dbcve.org
Puzzle Apps CmsApplication

CVE-2007-5147

MEDIUM · 6.8 CVSS v2.0 Published 2007-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Multiple PHP remote file inclusion vulnerabilities in Puzzle Apps CMS 2.2.1 allow remote attackers to execute arbitrary PHP code via a URL in the MODULEDIR parameter to (1) core/modules/my/my.module.php or (2) core/modules/xml/xml.module.php; the COREROOT parameter to (3) config.loader.php, (4) platform.loader.php, (5) core.loader.php, (6) person.loader.php, or (7) module.loader.php in core/ or (8) install/steps/step_3.php; or the THISDIR parameter to (9) people.lib.php, (10) general.lib.php, (11) content.lib.php, or (12) templates.lib.php in core/modules/admin/libs/ or (13) core/modules/webstat/MEC/index.php.

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

Remote File Inclusion (RFI) vulnerability in Puzzle Apps CMS 2.2.1 allows remote attackers to execute arbitrary PHP code by injecting a malicious URL through multiple parameters (MODULEDIR, COREROOT, THISDIR) across 13 different PHP files. Attackers can include remote PHP files that get executed on the server, leading to full system compromise.

MitigationFix requires input validation to ensure included files come from trusted local paths only, replacing dynamic path variables with hardcoded paths, and/or removing the vulnerable parameter usage entirely in all affected include() and require() 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
Puzzle Apps CmsApplication
Affected:= 2.2.1

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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. Identify if Puzzle Apps CMS is installed
    Search the web server document root for Puzzle Apps CMS files, typically in directories named 'puzzle', 'cms', or look for files containing 'Puzzle Apps CMS' branding or copyright text.
    Affected if Puzzle Apps CMS is found on the server
  2. Confirm the installed version is 2.2.1
    Check version.php, index.php, or any version/configuration file within the Puzzle Apps CMS directory for the version string '2.2.1'.
    Affected if The installed version is exactly 2.2.1
  3. Locate the vulnerable PHP files
    Search the CMS directory for the 13 affected PHP files that contain the MODULEDIR, COREROOT, or THISDIR parameters in include() or require() statements. Common paths include modules/, includes/, or core/ subdirectories.
    Affected if The vulnerable PHP files exist and are web-accessible
  4. Verify the RFI parameters are exposed
    Examine the identified PHP files to confirm they accept the MODULEDIR, COREROOT, or THISDIR parameters through GET or REQUEST superglobals and use them in dynamic include/require statements without validation.
    Affected if The parameters are used in dynamic include/require calls without sanitization
  5. Check if the web server can reach external URLs
    Review the PHP configuration (php.ini) for allow_url_fopen and allow_url_include settings, and verify network connectivity from the web server to potential attacker-controlled domains.
    Affected if allow_url_fopen or allow_url_include is enabled (allowing remote file inclusion)

You are affected if Puzzle Apps CMS version 2.2.1 is installed and the vulnerable PHP files with unprotected MODULEDIR, COREROOT, or THISDIR parameters are accessible on the web server with remote includes enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix requires input validation to ensure included files come from trusted local paths only, replacing dynamic path variables with hardcoded paths, and/or removing the vulnerable parameter usage entirely in all affected include() and require() calls.

Fix this in Puzzle Apps Cms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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