CVE-2007-4608
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 · uneditedPHP remote file inclusion vulnerability in protection.php in ePersonnel RC_2004_02 allows remote attackers to execute arbitrary PHP code via a URL in the logout_page parameter.
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 (RFI) vulnerability in ePersonnel RC_2004_02's protection.php allows attackers to execute arbitrary PHP code by supplying a malicious URL in the logout_page parameter, which is then included and executed by the PHP interpreter.
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= rc_2004_02CVSS 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.
-
Confirm ePersonnel RC_2004_02 installationLocate the ePersonnel application on your system by searching for the protection.php file or checking your web server document root for the 'epersonnel' or 'rc_2004_02' directory structure.Affected if The ePersonnel RC_2004_02 application directory exists on the server.
-
Identify protection.php and vulnerable parameterOpen the protection.php file in the ePersonnel installation directory and search for references to 'logout_page' to confirm the parameter is used in an include or require statement.Affected if The file contains code that includes or requires the logout_page parameter without sanitization.
-
Test parameter accessibilitySend an HTTP request to protection.php with a crafted logout_page parameter pointing to an external URL (for example: ?logout_page=http://example.com), and observe if the application attempts to include the external file.Affected if The application attempts to include the URL provided in the logout_page parameter.
-
Check PHP allow_url_include settingReview the php.ini configuration file for the allow_url_include directive. Execute 'php -i' or create a PHP info page to confirm the current setting.Affected if allow_url_include is enabled (set to On), making RFI attacks fully exploitable.
You are affected if ePersonnel RC_2004_02 is installed, protection.php uses the logout_page parameter in a dynamic include, and the application is accessible to untrusted input.
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 the logout_page parameter using a whitelist approach, or remove dynamic file inclusion entirely. Additionally, disable allow_url_include in php.ini as a defense-in-depth measure.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4608 — 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-4608 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