CVE-2026-5538
Received Received - Intake
Server-Side Request Forgery in QingdaoU OnlineJudge JudgeServer

Publication date: 2026-04-05

Last updated on: 2026-04-05

Assigner: VulDB

Description
A vulnerability was detected in QingdaoU OnlineJudge up to 1.6.1. Affected by this issue is the function service_url of the file JudgeServer.service_url of the component judge_server_heartbeat Endpoint. The manipulation results in server-side request forgery. It is possible to launch the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-05
Last Modified
2026-04-05
Generated
2026-05-07
AI Q&A
2026-04-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
qingdaou onlinejudge to 1.6.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-5538 is a stored Server-Side Request Forgery (SSRF) vulnerability in the QingdaoU OnlineJudge system, affecting versions up to 1.6.1. It exists in the judge_server_heartbeat API endpoint, specifically in the service_url parameter of the JudgeServer component.

An attacker with a valid judge server token can submit a malicious URL via the service_url parameter. This URL is stored in the database without proper validation or sanitization.

Later, when the system processes judge tasks, it uses the stored URL to make internal HTTP requests without re-validating it, allowing the attacker to force the server to make arbitrary requests to internal network resources.


How can this vulnerability impact me? :

This vulnerability allows an attacker to make the server perform arbitrary HTTP requests to internal network resources, which can lead to several security risks.

  • Exfiltration of sensitive metadata, such as cloud service metadata endpoints.
  • Internal network scanning to discover other vulnerable services or systems.
  • Potential remote code execution if the attacker can leverage the SSRF to interact with internal services that execute commands.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring and analyzing requests to the /api/admin/judge_server_heartbeat endpoint, especially POST requests containing the service_url parameter.

Since the vulnerability requires authentication with a valid judge server token, detection involves checking for unusual or unauthorized POST requests to this endpoint.

You can also inspect the JudgeServer table in the MySQL database for suspicious or unexpected URLs stored in the service_url field.

  • Use network monitoring tools (e.g., tcpdump, Wireshark) to capture POST requests to /api/admin/judge_server_heartbeat.
  • Run a SQL query to check stored URLs: SELECT service_url FROM JudgeServer WHERE service_url IS NOT NULL;
  • Check application logs for POST requests to /api/admin/judge_server_heartbeat with service_url parameters.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the /api/admin/judge_server_heartbeat endpoint to trusted users only, as the vulnerability requires authentication.

Review and sanitize any stored service_url values in the JudgeServer database to remove malicious URLs.

Implement network-level controls to prevent the server from making arbitrary HTTP requests to internal or sensitive endpoints.

Monitor and audit logs for suspicious activity related to the judge server heartbeat API.

If possible, apply patches or updates from the vendor once available, or consider disabling the vulnerable functionality until a fix is released.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

CVE-2026-5538 is a stored Server-Side Request Forgery (SSRF) vulnerability that allows authenticated attackers to make arbitrary internal HTTP requests via the QingdaoU OnlineJudge system. This can lead to sensitive metadata exfiltration and internal network scanning.

Such unauthorized access and potential data exfiltration could impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and prevention of unauthorized access or disclosure.

However, the provided information does not explicitly discuss compliance impacts or specific regulatory consequences.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart