CVE-2023-27073
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 · uneditedA Cross-Site Request Forgery (CSRF) in Online Food Ordering System v1.0 allows attackers to change user details and credentials via a crafted POST request.
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 confidenceCross-Site Request Forgery vulnerability in Online Food Ordering System v1.0 allows attackers to trick authenticated users into submitting crafted POST requests that modify their account details and credentials without their consent.
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= 1.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the installed product and versionInspect the application's main page, footer, or about/admin section for the product name 'Online Food Ordering System' by Oretnom23 and verify the version is 1.0Affected if The product is Oretnom23 Online Food Ordering System version 1.0
-
Identify user profile modification formsLocate forms in the application that allow users to modify their account details or credentials (typically found at /user/profile, /user/edit, /user/settings, or similar endpoints)Affected if The application has forms that allow modification of user profile information or passwords
-
Check for anti-CSRF tokens in profile formsView the HTML source code of the profile/credential modification forms and inspect whether a hidden input field containing a CSRF token, token parameter, or similar anti-CSRF mechanism is presentAffected if The form lacks a hidden CSRF token field or the form submission does not include a token parameter
-
Verify CSRF token is submitted with requestsSubmit a legitimate profile update request and inspect the HTTP request payload to confirm a CSRF token value is being sent along with the form dataAffected if The form submission does not include a token value in the request parameters
-
Check Origin/Referer header validationIf you have access to server-side logs or source code, inspect whether the application validates the Origin or Referer HTTP headers on POST requests to state-changing endpointsAffected if The server does not validate or reject requests with mismatched or missing Origin/Referer headers
The environment is affected if it runs Oretnom23 Online Food Ordering System v1.0 and the profile/credential modification forms lack anti-CSRF token protection.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms, particularly user profile and credential modification endpoints, and validate the Origin/Referer headers server-side.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27073 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-27073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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