CVE-2007-4339
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in PHPCentral Poll Script 1.0 allow remote attackers to execute arbitrary PHP code via a URL in the _SERVER[DOCUMENT_ROOT] parameter in (1) poll.php and (2) pollarchive.php. NOTE: a reliable third party states that this issue is resultant from a variable extraction error in functions.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 confidenceRemote file inclusion vulnerability in PHPCentral Poll Script 1.0 allows arbitrary PHP code execution via the _SERVER[DOCUMENT_ROOT] parameter in poll.php and pollarchive.php. The vulnerability stems from improper variable extraction (likely unsafe extract() or register_globals) in functions.php that allows attackers to override server variables and include malicious remote files.
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= 1.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify PHPCentral Poll Script installationLook for poll.php, pollarchive.php, and functions.php files in the web directory. Search for files containing 'PHPCentral' or the application's typical installation path.Affected if Any of the vulnerable files (poll.php, pollarchive.php, functions.php) are present on the system.
-
Confirm the installed versionOpen poll.php or any identified configuration file and search for a version string or number. Compare against the affected version 1.0.Affected if The installed version is exactly 1.0.
-
Check PHP register_globals settingCreate a PHP script with 'phpinfo();' or check the php.ini configuration file for 'register_globals = On'.Affected if register_globals is enabled in the PHP configuration.
-
Inspect functions.php for unsafe extract()Open functions.php and search for 'extract()' function calls without proper flags (such as EXTR_SKIP or EXTR_PREFIX_ALL) that could allow variable overwriting.Affected if functions.php contains extract() calls without security flags, allowing variable injection.
-
Verify variable handling in vulnerable filesExamine poll.php and pollarchive.php for direct use of _SERVER['DOCUMENT_ROOT'] or similar superglobals that could be overridden through extract() or register_globals.Affected if The code uses _SERVER variables that can be controlled via extracted/overridden variables.
The environment is affected if PHPCentral Poll Script version 1.0 is installed with vulnerable files accessible, combined with register_globals enabled or unsafe extract() usage in functions.php.
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 unsafe extract() calls or disable register_globals, implement proper input validation on all variables, and upgrade to a patched version if available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4339 — 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-2007-4339 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