CVE-2015-2974
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 · uneditedLEMON-S PHP Gazou BBS plus before 2.36 allows remote attackers to upload arbitrary HTML documents via vectors involving a crafted image file.
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 confidenceLEMON-S PHP Gazou BBS plus before version 2.36 contains an arbitrary file upload vulnerability. Attackers can upload arbitrary HTML documents by embedding HTML content within crafted image files, potentially enabling cross-site scripting (XSS) attacks or other client-side exploits.
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<= 2.35CVSS 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 the installed version of Lemon S Php Gazou BBS PlusLocate the version file or version identifier within the application installation directory. Common locations include a version.php file, a config file with a version parameter, or the main index file displaying the version in comments or metadata.Affected if The installed version is 2.35 or earlier (any version <= 2.35).
-
Verify the gazou.php or upload script exists and is accessibleCheck if the gazou.php upload script (or equivalent upload handler) exists in the web-accessible directory where the application is installed.Affected if The upload script is present and accessible without authentication or with weak access controls.
-
Check for file type validation in the upload scriptExamine the upload handling code (such as gazou.php or lib/upload.php) for validation logic that checks file content or MIME type. Look for functions that inspect the actual file content rather than just file extensions.Affected if No content-based validation is performed, or validation relies solely on file extension or client-provided MIME type without inspecting actual file content.
-
Determine if uploaded files are stored in a web-accessible locationIdentify the upload directory configuration and verify whether uploaded files are stored in a location accessible via HTTP/HTTPS.Affected if Uploaded files are stored in a web-accessible directory and can be directly accessed via URL.
You are affected if your installed version is 2.35 or earlier AND the upload functionality is accessible AND content validation is absent or insufficient.
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 dataUpgrade to version 2.36 or later. If upgrading is not possible, implement strict file type validation and content inspection to strip or reject HTML/script content from uploaded files.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2974 — 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-2015-2974 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