Secuno
ENNL
Book demo

CVE-2025-55849

Weiphp SQL injection

8.4 HIGHPublic exploitEPSS 0.20%
  1. Published8 Sept 2025

Description

WeiPHP v5.0 and before is vulnerable to SQL Injection via the SucaiController.class.php file and the cancelTemplatee

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Weiphp≤ 5.0

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-893028.6
The Post Voting System WordPress plugin through 1.0 does not properly sanitize and…
CVE-2026-892998.6
The WP Verify API WordPress plugin through 1.0.0 does not properly sanitize and escape…
CVE-2026-892978.6
The Loja Automática WordPress plugin through 1.0.0 does not properly sanitize and…
CVE-2026-892878.6
The ASPL Product Quotation WordPress plugin through 1.1.0 does not sanitize and escape…
CVE-2026-892858.6
The Datalist it WordPress plugin through 0.0.3 does not sanitize and escape several…
CVE-2026-892348.6
The WP-Partner WordPress plugin through 1.2.1 does not sanitise and escape a parameter…

Frequently asked

Is CVE-2025-55849 being actively exploited?

CVE-2025-55849 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.20%.

How severe is CVE-2025-55849?

CVE-2025-55849 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.20% probability of exploitation.

Which products are affected by CVE-2025-55849?

Affected products include Weiphp.

How do I fix CVE-2025-55849?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-55849 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.