LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30014: Lumidek Associates Simple Food Website 1.0 is vulnerable to Cross Site Request Forgery (CSRF) which allows...

Lumidek Associates Simple Food Website 1.0 is vulnerable to Cross Site Request Forgery (CSRF) which allows anyone to takeover admin/moderater account.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a CSRF issue in Lumidek Associates Simple Food Website 1.0 that could reportedly let an attacker take over an admin or moderator account. The public data is sparse: no CVSS score, fixed version, or detailed vendor advisory is provided.

Executive priority

Prioritize review if this software is used in production or exposed to privileged browser sessions. The impact is potentially serious account takeover, but urgency is tempered by incomplete public evidence and no cited exploitation.

Technical view

The record describes a cross-site request forgery flaw in Simple Food Website 1.0. A forged request could reportedly change privileged account state and lead to admin/moderator takeover. The provided sources do not include affected CPEs, endpoint details, prerequisites, CWE, CVSS vector, or patch information.

Likely exposure

Exposure appears limited to organizations running Simple Food Website 1.0, especially where administrative functions are reachable by browser-authenticated privileged users. The bundle lacks deployment identifiers, package names, and internet prevalence data.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked as CISA KEV. Practical risk depends on whether admins can be induced to visit attacker-controlled content while authenticated, and whether the application lacks CSRF defenses.

Researcher notes

The CVE record is thin and names no patch, endpoint, parameter, CPE, CVSS, or CWE. Treat the GitHub disclosure and CVE record as starting points, then validate exposure and remediation directly against the deployed application.

Mitigation direction

  • Inventory any Simple Food Website 1.0 deployments.
  • Check vendor or project guidance for fixed versions or mitigations.
  • Restrict administrative paths using VPN, SSO, or IP allowlists where feasible.
  • Ensure privileged actions require CSRF tokens and same-site cookie protections.
  • Review admin and moderator accounts for unauthorized changes.

Validation and detection

  • Confirm whether Simple Food Website 1.0 is deployed anywhere.
  • Review administrative forms for CSRF tokens and origin checks.
  • Verify privileged state changes require authenticated, intentional user action.
  • Check logs for unexpected admin or moderator account modifications.
  • Document any compensating access controls around admin routes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-30014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.