CVE-2019-25674
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 · uneditedCMSsite 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the 'post' parameter. Attackers can send GET requests to post.php with malicious 'post' values to extract sensitive database information or perform time-based blind SQL injection attacks.
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 confidenceCMSsite 1.0 has an unauthenticated SQL injection vulnerability in post.php where the 'post' parameter is directly used in SQL queries without sanitization. Attackers can exploit this via GET requests to inject SQL code, enabling extraction of sensitive database data or time-based blind SQL injection attacks.
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 CMSite version 1.0 is installedLocate the CMSite installation directory (commonly in web root such as /var/www/html/, /www/html/, or C:\inetpub\wwwroot\) and check for version indicators in source files, README, or configuration files. Look for version strings like '1.0' or 'CMSite v1.0'.Affected if The installed version is Victoralagwu Cmssite version 1.0 exactly.
-
Verify post.php exists in the applicationIn the CMSite installation directory, locate the file named 'post.php' - this is the vulnerable component mentioned in the CVE.Affected if The file post.php exists in the CMSite installation directory.
-
Check if the 'post' GET parameter is used in post.phpOpen post.php in a text editor and search for usage of $_GET['post'] or $post variable that is directly concatenated into SQL queries without visible sanitization functions (such as mysqli_real_escape_string, parameterized queries, or ORM methods).Affected if The code shows $_GET['post'] being used and directly embedded into SQL queries without prepared statements or proper escaping.
-
Confirm network accessibility of the vulnerable endpointAttempt to access http://[target]/post.php?post=test via curl or a browser. A 200 response indicates the application is reachable.Affected if The post.php endpoint is accessible over the network and returns application content.
If CMSite version 1.0 is installed, post.php exists, the 'post' GET parameter is used in unsanitized SQL queries, and the endpoint is network-accessible, then the environment is affected by CVE-2019-25674.
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 database operations in post.php to prevent SQL injection. Apply input validation and ensure the 'post' parameter is properly escaped or bound as a parameter before executing any SQL queries.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25674 — 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-2019-25674 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