Secuno
ENNL
Book demo

CVE-2025-70821

Renren Renren-security SQL injection

9.8 CRITICALPublic exploitEPSS 0.41%
  1. Published3 Mar 2026

Description

renren-secuity before v5.5.0 is vulnerable to SQL Injection in the BaseServiceImpl.java component

CVSS 3.1 breakdown

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

Affected products

Renren Renren-security≤ 5.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-891138.8
SAP Commerce Cloud does not sufficiently validate certain user-supplied input before it…
CVE-2026-1096088.8
Frappe ERPNext before 15.121.0 and 16.x before 16.34.0 contains an SQL injection…
CVE-2026-1095738.1
phpMyFAQ before 4.1.9 contains an SQL injection vulnerability in PdoMysql::escape(),…
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…

Frequently asked

Is CVE-2025-70821 being actively exploited?

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

How severe is CVE-2025-70821?

CVE-2025-70821 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2025-70821?

Affected products include Renren Renren-security.

How do I fix CVE-2025-70821?

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