Skip to main content
VulnerabilityPublished

CVE-2025-15498: Pro3W CMS · SQL Injection

Affects Pro3W CMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Pro3WPro3W CMSAffected
  • <=1.2.0
Fixed in–

AI-suggested

To mitigate CVE-2025-15498, organizations should prioritize upgrading to the fixed Pro3W CMS version released in January 2026 or later as soon as it becomes available. Until patches are applied, implement the following compensating controls: 1) Restrict external access to the CMS login interface using network-level controls such as IP whitelisting or VPN access. 2) Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the login form. 3) Conduct thorough input validation and sanitization on all user inputs at the application layer, if possible through custom code or middleware. 4) Monitor CMS logs and network traffic for unusual login attempts or injection payloads. 5) Employ multi-factor authentication (MFA) on administrative accounts to reduce the impact of potential credential compromise. 6) Regularly back up CMS data and configurations to enable rapid recovery in case of compromise. 7) Engage in proactive threat hunting and vulnerability scanning focused on SQL injection vectors within the CMS environment. These measures will reduce exposure until official patches are deployed.

Description

Pro3W CMS if vulnerable to SQL injection attacks. Improper neutralization of input provided into a login form allows an unauthenticated attacker to bypass authentication and gain administrative privileges.  This issue was identified in version 1.2.0 of this software. Due to lack of response from the vendor exact version range could not be determined, but the vulnerability should be eliminated in versions released in January 2026 and later.

References

Community reviews

Loading reviews…