CVE-2022-3015
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 vulnerability, which was classified as problematic, has been found in oretnom23 Fast Food Ordering System. This issue affects some unknown processing of the file admin/?page=reports. The manipulation of the argument date leads to cross site scripting. The attack may be initiated remotely. The identifier VDB-207425 was assigned to this vulnerability.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the oretnom23 Fast Food Ordering System where the date parameter in the admin/?page=reports endpoint does not properly sanitize user input, allowing attackers to inject malicious JavaScript code.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Fast Food Ordering System is installedLook for the application in your web root directory. Common paths include /var/www/html/, /wwwroot/, or the document root. Search for files containing 'Fast Food Ordering System' in page titles or meta tags, or check for the presence of admin/login.php, admin/?page=reports, or similar admin directory structures.Affected if The application directory contains the Fast Food Ordering System by oretnom23, specifically the admin interface with reports functionality.
-
Verify the version is 1.0Check for version indicators in the application. Look in README.md, VERSION file, or config files for version strings. Also check the page source of any admin page for version comments or meta tags.Affected if The installed version is exactly 1.0, which matches the affected version range.
-
Confirm admin reports endpoint existsAccess the URL path admin/?page=reports in your browser or via curl. Check if the page loads and displays date-related reporting functionality.Affected if The admin/?page=reports endpoint exists and returns a valid page with date input fields.
-
Test the date parameter for XSS vulnerabilitySubmit a test payload to the date parameter in the reports page. Example: Visit admin/?page=reports&date=%3Cscript%3Ealert(1)%3C/script%3E and check if the script tag is reflected unmodified in the page response.Affected if The date parameter reflects user-supplied input without sanitization, allowing script execution.
You are affected if the Fast Food Ordering System version 1.0 is installed and the admin/?page=reports endpoint reflects the date parameter unsanitized in the response.
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 input validation and output encoding for the date parameter, and consider deploying Content Security Policy (CSP) headers to mitigate XSS attacks.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3015 — 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-2022-3015 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