CVE-2015-2970
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 · uneditedindex.php in LEMON-S PHP Simple Oekaki BBS before 1.21 allows remote attackers to delete arbitrary files via the oekakis 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 confidenceThe index.php script in LEMON-S PHP Simple Oekaki BBS before version 1.21 contains a vulnerability where the oekakis parameter is not properly validated, allowing remote attackers to specify arbitrary file paths and delete any file accessible to the web server process.
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.2CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Lemon S Php Simple OekakiSearch for version information in index.php, any README file, or the application header/footer. Look for strings like 'version', 'ver', or '1.2' within the application directory.Affected if The version is 1.2 or lower, or no version information is found (unknown versions should be treated as affected).
-
Confirm the presence of the vulnerable index.php fileLocate the index.php file in the web-accessible directory where Lemon S Php Simple Oekaki is installed. This is the script containing the vulnerability.Affected if The file index.php exists in the web application directory.
-
Verify the application is web-exposedDetermine if the application directory is accessible via HTTP/HTTPS requests to the web server. This is required for remote exploitation.Affected if The application is accessible over the network (not restricted to localhost or blocked by authentication).
-
Check the oekakis parameter handling in index.phpExamine index.php source code and look for the oekakis parameter processing. Search for code that handles this parameter, particularly file deletion operations or path handling.Affected if The oekakis parameter is processed without proper validation, allowing arbitrary file paths to be specified (this would indicate an unpatched version).
You are affected if Lemon S Php Simple Oekaki version 1.2 or lower is installed and the application is accessible via the web, since the unpatched index.php allows arbitrary file deletion through the oekakis parameter.
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 1.21 or later which contains the patch for this vulnerability. As a temporary measure, restrict web server permissions to limit file deletion capabilities and monitor for suspicious delete operations.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2970 — 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-2970 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