CVE-2018-25199
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 · uneditedOOP CMS BLOG 1.0 contains SQL injection vulnerabilities that allow unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through multiple parameters. Attackers can inject SQL commands via the search parameter in search.php, pageid parameter in page.php, and id parameter in posts.php to extract database information including table names, schema names, and database credentials.
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 confidenceOOP CMS BLOG 1.0 has critical SQL injection vulnerabilities in three files. Unauthenticated attackers can inject arbitrary SQL commands through the search parameter in search.php, the pageid parameter in page.php, and the id parameter in posts.php. This allows complete database compromise including extraction of table names, schema, and credentials.
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.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm product and versionIdentify the installed version of Tomalofficial Php Oop Cms Blog. Check for any version file, README, or admin panel that displays the CMS version.Affected if The installed version is 1.0
-
Locate vulnerable PHP filesSearch the web root for the presence of search.php, page.php, and posts.php files which contain the SQL injection vulnerabilities.Affected if All three files (search.php, page.php, posts.php) exist in the web-accessible directory
-
Verify parameter exposureExamine if the search, pageid, and id parameters are accepted via GET or POST requests without authentication. Test accessing these endpoints directly.Affected if The search.php, page.php, and posts.php endpoints are accessible without authentication and accept user input through the search, pageid, and id parameters respectively
-
Check input handling in database queriesReview the source code of search.php, page.php, and posts.php to verify whether user-supplied parameters (search, pageid, id) are used directly in SQL queries without prepared statements, parameterization, or proper escaping.Affected if The parameters are concatenated directly into SQL queries without sanitization or prepared statements
The environment is affected if running Tomalofficial Php Oop Cms Blog version 1.0 with the vulnerable search.php, page.php, and posts.php files accessible and processing unsanitized user input into SQL queries.
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 prepared statements/parameterized queries for all user inputs in search.php, page.php, and posts.php. Validate and sanitize all parameters before database queries. Consider applying a web application firewall as an additional layer of defense.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25199 — 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-2018-25199 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