dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-4200

HIGH · 7.3 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in glowxq glowxq-oj up to 6f7c723090472057252040fd2bbbdaa1b5ed2393. This affects the function uploadTestcaseZipUrl of the file business/business-oj/src/main/java/com/glowxq/oj/problem/controller/ProblemCaseController.java. Performing a manipulation results in server-side request forgery. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the uploadTestcaseZipUrl function of ProblemCaseController.java in glowxq-oj. The function likely accepts user-supplied URLs without proper validation, allowing an attacker to manipulate the server into making requests to arbitrary internal or external resources, potentially accessing sensitive internal services or exfiltrating data.

MitigationImplement strict input validation with allowlist-based URL validation for the uploadTestcaseZipUrl function, restrict outgoing network requests, and apply network segmentation to limit the impact of SSRF attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if glowxq-oj is deployed
    Search for files named glowxq-oj, check running Java processes for the application jar/war, or look for the project directory containing ProblemCaseController.java
    Affected if The system runs the glowxq-oj online judge application
  2. Locate the vulnerable function
    Search the codebase for the file ProblemCaseController.java and confirm the presence of the uploadTestcaseZipUrl method
    Affected if The uploadTestcaseZipUrl function exists in the codebase and is compiled into the running application
  3. Verify the upload endpoint is accessible
    Check application routing/configuration for endpoints mapped to uploadTestcaseZipUrl (commonly paths like /problem/case/upload or /api/problem/upload). Test if the endpoint responds to HTTP requests.
    Affected if The endpoint handling uploadTestcaseZipUrl is exposed and reachable via HTTP/HTTPS
  4. Confirm no URL validation exists
    Review the uploadTestcaseZipUrl function code for URL validation logic (allowlists, hostname checks, protocol restrictions). Look for input sanitization before making HTTP requests.
    Affected if The function accepts arbitrary URLs without strict validation or allowlist-based filtering
  5. Check network configuration
    Review if the application has network restrictions configured (firewall rules, egress controls, or application-level network policies)
    Affected if The server can make outbound HTTP requests without restriction, allowing potential SSRF exploitation

A user is affected if glowxx-oj is deployed and the uploadTestcaseZipUrl endpoint accepts user-supplied URLs without strict validation, allowing the server to be coerced into making arbitrary HTTP requests to internal or external resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation with allowlist-based URL validation for the uploadTestcaseZipUrl function, restrict outgoing network requests, and apply network segmentation to limit the impact of SSRF attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4200 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data