dbcve.org
Vikrestaurants Table Reservations And Take AwayWordPress extension · E4jconnect

CVE-2025-46251

HIGH · 8.8 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 e4jvikwp VikRestaurants vikrestaurants allows Cross Site Request Forgery.This issue affects VikRestaurants: from n/a through <= 1.3.3.

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

CSRF vulnerability in VikRestaurants <= 1.3.3 allows attackers to induce authenticated users to perform unintended state-changing actions by tricking them into submitting malicious requests. The lack of anti-CSRF tokens on sensitive operations enables forged requests to be executed without the user's knowledge.

MitigationImplement synchronizer token pattern (anti-CSRF tokens) on all state-changing forms and validate tokens server-side; additionally configure SameSite cookie attributes and validate Origin/Referer headers.

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
Vikrestaurants Table Reservations And Take AwayWordPress extension
Affected:< 1.4

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

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

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 installed VikRestaurants version
    Access the administrator dashboard and navigate to Components > VikRestaurants, or check the extension manifest file (typically xml file in /administrator/components/com_vikrestaurants/) for the version attribute
    Affected if version is 1.3.3 or lower (any version < 1.4)
  2. Verify vulnerable version range
    Compare your installed version number against the affected range: any version prior to 1.4.0 is considered vulnerable
    Affected if installed version is less than 1.4.0
  3. Inspect state-changing forms for anti-CSRF tokens
    Examine HTML source of forms that perform state-changing operations (such as reservation management, menu configuration, user settings). Look for hidden input fields containing tokens (commonly named 'csrf', 'token', 'csrftoken', or similar) within <form> tags
    Affected if forms lack hidden CSRF token fields and the application does not validate anti-CSRF tokens server-side
  4. Test token validation on form submission
    Submit a legitimate form request without the anti-CSRF token (or with a forged token) using a tool like Burp Suite or curl to a state-changing endpoint; observe whether the request is accepted despite missing/invalid tokens
    Affected if requests are processed successfully without valid anti-CSRF tokens

You are affected if VikRestaurants version is below 1.4.0 and state-changing forms lack anti-CSRF token validation.

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.

dbcve · scoped
Upgrade available Upgrade to 1.4 or later
Fixed in 1.4
Interim mitigation

Implement synchronizer token pattern (anti-CSRF tokens) on all state-changing forms and validate tokens server-side; additionally configure SameSite cookie attributes and validate Origin/Referer headers.

Recommended fix High confidence

VikRestaurants 1.4 or later

  1. 1. Back up your website and database before performing any updates.
  2. 2. Navigate to the Joomla! extension manager or the VikRestaurants update mechanism.
  3. 3. Check for available updates for VikRestaurants component.
  4. 4. Update VikRestaurants to version 1.4 or the latest available version.
  5. 5. Verify the update was successful by checking the component version in the Joomla! administrator panel.
  6. 6. Test critical reservation and ordering workflows to ensure functionality is intact.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vikrestaurants Table Reservations And Take Away Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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