Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-25674: CMSsite 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate databa

47
This week
HIGH 8.2REMOTEDOWNGRADE

CVE-2019-25674 is a high-severity flaw (CVSS 8.2) affecting cmssite. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 65%)
CISA exploited listNo
WeaknessCWE-89
Published2026-04-05
Last modified2026-07-24
Publisher (CNA): VulnCheck · Vendor: victoralagwu

Share: LinkedIn · X · Reddit

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

victoralagwu cmssite DOWNGRADE
Affected: 1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy cmssite || rpm -q cmssite || cmssite --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison cmssite sudo apt install cmssite=<VERSION_BEFORE_1.0> sudo apt-mark hold cmssite
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list cmssite sudo dnf downgrade cmssite-<VERSION_BEFORE_1.0> sudo dnf versionlock add cmssite
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25674?

cmssite: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-25674 being exploited?

CVE-2019-25674 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25674 affect?

CVE-2019-25674 affects cmssite. Severity is high (CVSS 8.2). 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' v

How urgent is CVE-2019-25674?

Priority 47/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.