dbcve.org
Online Food Delivery SystemApplication · Restajet

CVE-2025-1927

HIGH · 7.1 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 →
77/100
Remediation priority · High
Remotely reachable 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
Cross-Site Request Forgery (CSRF) vulnerability in Restajet Information Technologies Inc. Online Food Delivery System allows Cross Site Request Forgery. 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

Cross-Site Request Forgery (CSRF) vulnerability in Restajet Online Food Delivery System allows attackers to trick authenticated users into submitting unintended requests, potentially performing unauthorized actions like placing orders or modifying account data.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations, or utilize SameSite cookie attributes, and ensure proper validation on the server side for all POST/PUT/DELETE requests.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

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

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 Restajet installation
    Locate the Restajet application files or confirm the service is running. Check for the typical installation directory or running web server process serving Restajet.
    Affected if Restajet Online Food Delivery System is present and accessible in the environment
  2. Inspect HTML forms for CSRF tokens
    Navigate to pages with state-changing operations (order placement, account modification, user profile updates). View the page source (right-click > View Page Source) and search for input fields containing 'csrf', 'token', 'anticsrf', or similar anti-CSRF token patterns within the <form> tags.
    Affected if No hidden input field with a token value is present in forms that perform POST/PUT/DELETE actions
  3. Verify token presence on order submission
    Submit an order or perform a purchase transaction. Intercept the request (using browser DevTools or a proxy) and examine the POST data sent to the server. Look for a token parameter in the request body.
    Affected if The POST request contains no anti-CSRF token parameter in the request body
  4. Check cookie SameSite attribute
    Open browser DevTools (F12), go to Application tab > Cookies. Examine cookies set by the Restajet domain. Check if the SameSite attribute is set to 'Strict' or 'Lax' on session/authentication cookies.
    Affected if Session cookies either have no SameSite attribute set or explicitly have SameSite=None without Secure flag, indicating CSRF protection via cookie attributes is missing
  5. Test for CSRF vulnerability
    Create a simple HTML page with a form that auto-submits to a Restajet state-changing endpoint (e.g., /order/submit or /user/update). Host this on another domain and attempt to trigger it from an authenticated browser session.
    Affected if The action is successfully executed without the server rejecting the request due to missing CSRF validation, confirming the vulnerability exists

If Restajet is running and state-changing requests (orders, account changes) lack anti-CSRF tokens or proper SameSite cookie attributes, the environment is affected by CVE-2025-1927.

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 anti-CSRF tokens (synchronizer token pattern) on all state-changing operations, or utilize SameSite cookie attributes, and ensure proper validation on the server side for all POST/PUT/DELETE requests.

Fix this in Online Food Delivery System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1927 — 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-2025-1927 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