Online Food Delivery SystemApplication · Restajet

CVE-2025-1885

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Restajet Information Technologies Inc. Online Food Delivery System allows Phishing, Forceful Browsing. This issue affects Online Food Delivery System: through 19122025. NOTE: 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

The Online Food Delivery System by Restajet contains an open redirect vulnerability where user-supplied input is used to determine the destination of a redirect without proper validation. Attackers can craft malicious URLs that appear to originate from the legitimate site but redirect users to attacker-controlled domains, facilitating phishing and forceful browsing attacks.

MitigationImplement strict validation of redirect parameters using an allowlist of permitted destinations, or remove the redirect functionality if not essential. All user-controlled redirect targets should be validated against a whitelist of approved domains or relative paths.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Food Delivery SystemApplication
Affected:all versions

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
Low
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/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 redirect functionality in the application
    Search the codebase for redirect-related functions or methods (such as 'header()', 'redirect()', 'Location:', or similar functions) and identify any parameters that accept user input and are used as redirect targets.
    Affected if The application uses user-supplied parameters to control redirect destinations without validation.
  2. Examine redirect handling code
    Review the code that processes redirect requests and check whether it validates the destination URL against an allowlist or restricts redirects to relative paths only.
    Affected if No validation or allowlist check is performed before performing the redirect.
  3. Check for vulnerable redirect parameters
    Identify parameters in the application (such as 'redirect', 'url', 'next', 'dest', 'destination', or 'return_url') that accept URL values and trace how they are used in redirect operations.
    Affected if User-controlled parameters are directly used in redirect operations without sanitization.
  4. Test for open redirect behavior
    If accessible, provide a parameter value containing an external domain (such as 'https://attacker.com') to a suspected redirect endpoint and observe whether the application redirects to that arbitrary domain.
    Affected if The application redirects to externally provided domains without warning or validation.

Your environment is affected if the Restajet Online Food Delivery System has redirect functionality that uses user-supplied input to determine the redirect destination without validating against an allowlist of permitted domains or paths.

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 validation of redirect parameters using an allowlist of permitted destinations, or remove the redirect functionality if not essential. All user-controlled redirect targets should be validated against a whitelist of approved domains or relative paths.

Fix this in Online Food Delivery System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-1885 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