dbcve.org
Photopost Php ProApplication · Photopost

CVE-2006-4990

HIGH · 7.5 CVSS v2.0 Published 2006-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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 PhotoPost allow remote attackers to execute arbitrary PHP code via a URL in the PP_PATH parameter in (1) addfav.php, (2) adm-admlog.php, (3) adm-approve.php, (4) adm-backup.php, (5) adm-cats.php, (6) adm-cinc.php, (7) adm-db.php, (8) adm-editcfg.php, (9) adm-inc.php, (10) adm-index.php, (11) adm-modcom.php, (12) adm-move.php, (13) adm-options.php, (14) adm-order.php, (15) adm-pa.php, (16) adm-photo.php, (17) adm-purge.php, (18) adm-style.php, (19) adm-templ.php, (20) adm-userg.php, (21) adm-users.php, (22) bulkupload.php, (23) cookies.php, (24) comments.php, (25) ecard.php, (26) editphoto.php, (27) register.php, (28) showgallery.php, (29) showmembers.php, (30) useralbums.php, (31) uploadphoto.php, (32) search.php, or (33) adm-menu.php, different vectors than CVE-2006-4828.

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

This is a Remote File Inclusion (RFI) vulnerability in PhotoPost PHP applications where the PP_PATH parameter is not properly validated in 33 different PHP files. Attackers can supply a malicious URL in the PP_PATH parameter to include and execute arbitrary PHP code on the server.

MitigationDisable or remove the PP_PATH parameter usage entirely, or implement strict whitelist-based input validation to ensure only trusted local paths are accepted. Upgrading to a patched version of PhotoPost if available is recommended.

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
Photopost Php ProApplication
Affected:= 4.5= 4.6

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if PhotoPost is installed
    Look for PhotoPost PHP directories or files on the web server. Common paths include /photopost/, /gallery/, or search for 'photopost' in file names.
    Affected if PhotoPost PHP Pro files are found on the server
  2. Determine the installed PhotoPost version
    Open the main PhotoPost PHP file (such as index.php, pp.php, or a version.php file) and look for a version string. Search for patterns like '4.5', '4.6', or 'Version:' in the source code.
    Affected if The installed version is 4.5 or 4.6
  3. Locate PHP files that use the PP_PATH parameter
    Search the PhotoPost directory for PHP files containing 'PP_PATH' by using grep or a text search: grep -r 'PP_PATH' /path/to/photopost/
    Affected if PP_PATH parameter handling code is found in multiple PHP files within the PhotoPost installation
  4. Check if the application is network-accessible
    Determine if the PhotoPost web directory is accessible from external networks by attempting to access the site URL or reviewing web server configuration for exposed virtual hosts.
    Affected if The PhotoPost application is accessible from the internet or untrusted networks

A system is affected if PhotoPost PHP Pro versions 4.5 or 4.6 are installed and the PP_PATH parameter handling is active in the PHP files.

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

Disable or remove the PP_PATH parameter usage entirely, or implement strict whitelist-based input validation to ensure only trusted local paths are accepted. Upgrading to a patched version of PhotoPost if available is recommended.

Fix this in Photopost Php Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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