dbcve.org
PhpadsnewApplication

CVE-2005-0790

MEDIUM · 5.0 CVSS v2.0 Published 2005-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
phpAdsNew 2.0.4 allows remote attackers to obtain sensitive information via a direct request to (1) lib-xmlrpcs.inc.php, (2) maintenance-activation.php, (3) maintenance-cleantables.php, (4) maintenance-autotargeting.php, (5) maintenance-reports.php, (6) phpads.php, (7) remotehtmlview.php, (8) click.php, (9) adcontent.php, which reveal the path in a PHP error message.

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

phpAdsNew 2.0.4 contains multiple PHP files that reveal the server's filesystem path when accessed directly. These files (lib-xmlrpcs.inc.php, maintenance-activation.php, maintenance-cleantables.php, maintenance-autotargeting.php, maintenance-reports.php, phpads.php, remotehtmlview.php, click.php, adcontent.php) lack proper include guards or initialization checks, causing PHP to emit error messages containing full path information when dependencies are not loaded.

MitigationDisable PHP error display in production (display_errors=Off) and add direct-access prevention checks (e.g., defining an initialization constant before includes) to each affected file to prevent standalone execution.

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
PhpadsnewApplication
Affected:= 2.0.4_pr1

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 checks

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

  1. Identify if phpAdsNew is installed
    Search for phpAdsNew installation directories (e.g., /adserver, /phpadsnew, /banner) or check web server document roots for phpAdsNew-related files and directories.
    Affected if phpAdsNew is present on the server
  2. Determine the installed phpAdsNew version
    Check the version.php or config file within the phpAdsNew installation directory, or examine any version identifiers in the source files.
    Affected if The installed version is 2.0.4_pr1
  3. Locate the affected PHP files
    Verify the presence of these files within the phpAdsNew installation: lib-xmlrpcs.inc.php, maintenance-activation.php, maintenance-cleartables.php, maintenance-autotargeting.php, maintenance-reports.php, phpads.php, remotehtmlview.php, click.php, adcontent.php
    Affected if Any of the listed files exist in the installation
  4. Test for direct access vulnerability
    Attempt to access one or more affected files directly via HTTP (e.g., http://yourserver/path/to/phpadsnew/click.php) and observe if PHP error messages containing filesystem paths are returned.
    Affected if Direct access to any affected file produces error output with full server filesystem paths
  5. Check PHP error display configuration
    Examine php.ini or check the runtime configuration for display_errors setting. If On, error messages will reveal path information.
    Affected if display_errors is enabled (On) in PHP configuration

A server is affected if phpAdsNew 2.0.4_pr1 is installed with the vulnerable files present and accessible, especially if PHP display_errors is 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

Disable PHP error display in production (display_errors=Off) and add direct-access prevention checks (e.g., defining an initialization constant before includes) to each affected file to prevent standalone execution.

Fix this in Phpadsnew Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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