LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25674: CMSsite 1.0 SQL Injection via post Parameter

CMSsite 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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CMSsite 1.0 has a high-severity SQL injection flaw in the unauthenticated “post” parameter. An attacker could manipulate database queries and potentially read sensitive data. Public exploit information exists, but the provided sources do not show confirmed active exploitation.

Executive priority

Treat as a near-term priority if CMSsite 1.0 is deployed, because it is remotely reachable without authentication and can expose database contents. If the product is not in use, business urgency is low.

Technical view

CVE-2019-25674 is CWE-89 SQL injection in CMSsite 1.0. The CVSS 4.0 score is 8.8. The issue is remotely reachable over the network, requires no privileges or user interaction, and affects confidentiality heavily with limited integrity impact. Sources describe GET requests to post.php using the post parameter.

Likely exposure

Exposure is likely limited to organizations running VictorAlagwu CMSsite 1.0, especially if post.php is internet-accessible. The source bundle does not identify other affected versions, packaged distributions, or hosted services.

Exploitation context

ExploitDB is cited as an exploit reference, so public exploit material exists. The CVE is not marked KEV, and the provided sources do not confirm active exploitation in the wild.

Researcher notes

Evidence is limited to the CVE record, VulnCheck advisory, ExploitDB reference, and the GitHub product page. No source in the bundle names a fixed version, patch commit, or confirmed exploitation campaign.

Mitigation direction

  • Identify whether CMSsite 1.0 is deployed in any environment.
  • Restrict public access to CMSsite until vendor guidance is reviewed.
  • Check the project repository and advisory sources for patches or upgrade guidance.
  • Apply input validation and parameterized database queries if maintaining the code internally.
  • Monitor database and web logs for suspicious post.php access patterns.

Validation and detection

  • Inventory web applications for CMSsite 1.0 or cloned deployments.
  • Confirm whether post.php is reachable from untrusted networks.
  • Review application code handling the post parameter for unsafe SQL construction.
  • Check WAF, web, and database logs for unusual query behavior.
  • Validate remediation through safe code review or authorized non-destructive testing.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25674 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2019-25674Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VictorAlagwuCMSsite1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.