CVE-2007-2780
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 · uneditedPsychoStats 3.0.6b and earlier allows remote attackers to obtain sensitive information via a request for server.php with a missing or invalid newtheme parameter, which reveals a path in an 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 confidencePsychoStats 3.0.6b and earlier contains a path disclosure vulnerability in server.php where a missing or invalid newtheme parameter causes the application to leak absolute file paths in error messages. This information can aid attackers in reconnaissance for further exploitation.
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<= 3.0.6b= 2.0= 2.0.1= 2.1= 2.2= 2.2.1= 2.2.2= 2.2.4= 2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PsychoStats versionCheck your installation for version files or view the main index.php / header files which typically display the version numberAffected if Version is 3.0.6b or earlier, or matches 2.0, 2.0.1, 2.1, 2.2, 2.2.1, 2.2.2, 2.2.4, or 2.3
-
Locate server.php fileFind the server.php file within your PsychoStats web root directoryAffected if server.php exists in the web-accessible directory
-
Test newtheme parameter for path disclosureSend a request to server.php without the newtheme parameter or with an invalid value, for example: http://yourserver.com/server.php or http://yourserver.com/server.php?newtheme=invalidAffected if The response displays absolute file paths in error messages or warnings
-
Check PHP error reporting configurationReview your php.ini or .htaccess for error_reporting and display_errors settings; look for E_ALL or E_WARNING enabled in productionAffected if Error display is enabled and PHP reveals full system paths in messages
-
Inspect server.php source codeOpen server.php and search for code that handles the newtheme parameter, looking for include/require statements that may use unsanitized inputAffected if The code uses the newtheme parameter in file inclusion without validation and error handling reveals full paths
Your environment is affected if you run a PsychoStats version listed as vulnerable AND the server.php script exposes absolute file paths when the newtheme parameter is missing or invalid.
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 proper input validation for the newtheme parameter and configure error handling to display generic messages rather than revealing system paths. Upgrade to a patched version if available.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2780 — 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-2780 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