CVE-2005-2413
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 apa_phpinclude.inc.php in Atomic Photo Album (APA) allows remote attackers to execute arbitrary PHP code via the apa_module_basedir 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 confidencePHP remote file inclusion vulnerability in apa_phpinclude.inc.php of Atomic Photo Album allows remote attackers to execute arbitrary PHP code by supplying a malicious URL via the apa_module_basedir parameter, which gets 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= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.1.0_pre1= 1.1.0_pre2= 1.1.0_pre3= 1.1.0_pre4CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 installed Atomic Photo Album versionLocate the application directory and check version.php, CHANGELOG, or README files for version informationAffected if The installed version matches 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.1.0_pre1, 1.1.0_pre2, 1.1.0_pre3, or 1.1.0_pre4
-
Verify apa_phpinclude.inc.php existsSearch for the file apa_phpinclude.inc.php within the web application directory structure, typically under include/ or similar pathsAffected if The file exists in the application installation
-
Check if the vulnerable parameter is reachableReview web server logs or application access logs for requests containing 'apa_module_basedir' parameter, or attempt a benign test request to the script handling this parameterAffected if The apa_module_basedir parameter is accepted and processed by the application
-
Inspect PHP configuration for remote inclusion settingsCheck php.ini or use phpinfo() to verify the values of allow_url_fopen and allow_url_include settingsAffected if Either allow_url_fopen or allow_url_include is enabled (set to On or 1)
You are affected if Atomic Photo Album version 1.0 through 1.1.0_pre4 is installed, the apa_phpinclude.inc.php file exists, the apa_module_basedir parameter is processed, and PHP allows remote URL inclusions.
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 dataDisable PHP's allow_url_fopen and allow_url_include settings, implement strict input validation on the apa_module_basedir parameter to restrict it to expected values, or replace dynamic includes with a whitelist-based include mechanism.
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2413 — 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-2005-2413 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