Skip to main content
CVE-2025-64280VulnerabilityPublished Updated

CVE-2025-64280: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

AI-suggested

Given the absence of an official patch, European organizations should implement immediate mitigations including: 1) Deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the permit_no parameter. 2) Applying strict input validation and sanitization on all user-supplied data fields, especially permit_no, to reject malicious payloads. 3) Restricting database permissions for the application account to the minimum necessary to limit damage from successful injection. 4) Monitoring logs and network traffic for unusual query patterns or spikes in errors related to database operations. 5) Segmenting the network to isolate the affected application servers from sensitive backend systems. 6) Preparing for rapid patch deployment once CentralSquare releases an official fix. 7) Conducting security awareness training for IT staff to recognize and respond to exploitation attempts. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and operational context.

Description

A SQL Injection Vulnerability in CentralSquare Community Development 19.5.7 allows attackers to inject SQL via the permit_no field.

References

Community reviews

Loading reviews…