CVE-2025-70821
Received Received - Intake
SQL Injection in renren-security BaseServiceImpl Before v

Publication date: 2026-03-03

Last updated on: 2026-03-05

Assigner: MITRE

Description
renren-secuity before v5.5.0 is vulnerable to SQL Injection in the BaseServiceImpl.java component
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-03
Last Modified
2026-03-05
Generated
2026-06-16
AI Q&A
2026-03-03
EPSS Evaluated
2026-06-15
NVD
CVE-2025-70821
EUVD
EUVD-2025-208233
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
renren renren-security to 5.5.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

[{'type': 'paragraph', 'content': 'CVE-2025-70821 is a SQL Injection vulnerability found in the renren-security product version 5.5.0 and earlier. It occurs in the BaseServiceImpl.java component, specifically exploitable via the "orderField" parameter. An attacker can inject malicious SQL code through this parameter, which may allow unauthorized database queries or manipulation.'}, {'type': 'paragraph', 'content': 'A proof of concept demonstrates a time-based blind SQL injection technique where the injected payload checks for the existence of a database table and triggers a delay if it exists, confirming the vulnerability.'}] [1, 2]

Impact Analysis

This SQL Injection vulnerability can allow an attacker to execute arbitrary SQL commands on the affected database. This may lead to unauthorized data access, data leakage, data modification, or even complete compromise of the database.

Such an attack could result in sensitive information exposure, loss of data integrity, and potential disruption of service.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by sending specially crafted HTTP requests to the vulnerable endpoint and observing the response behavior. Specifically, the SQL injection is exploitable via the "orderField" parameter in the endpoint `/renren-admin/sys/scheduleLog/page`.'}, {'type': 'paragraph', 'content': 'A common detection technique is to use a time-based blind SQL injection payload that causes a delay if the injection is successful. For example, injecting a payload that checks for the existence of a table in the database and triggers a sleep delay can confirm the vulnerability.'}, {'type': 'paragraph', 'content': 'An example command using curl to test this might be:'}, {'type': 'list_item', 'content': 'curl -X POST "http://target-server:8080/renren-admin/sys/scheduleLog/page" -H "token: your_token_here" -d "orderField=if((select count(*) from INFORMATION_SCHEMA.TABLES where table_name=\'COLUMNS\')>0,sleep(3),0)"'}, {'type': 'paragraph', 'content': 'If the response is delayed by approximately 3 seconds, it indicates the presence of the SQL injection vulnerability.'}] [1]

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-70821. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart