CVE-2025-22670
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 · uneditedMissing Authorization vulnerability in e4jvikwp VikBooking Hotel Booking Engine & PMS vikbooking allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects VikBooking Hotel Booking Engine & PMS: from n/a through <= 1.7.2.
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 confidenceMissing authorization vulnerability in VikBooking Hotel Booking Engine & PMS allows authenticated or unauthenticated attackers to access resources or perform actions beyond their intended privileges due to incorrectly configured access control security levels in versions up to 1.7.2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Identify VikBooking installation and versionLocate the VikBooking installation directory and check the version file (commonly version.php or similar version declaration in the main component file). In Joomla installations, check the component manifest or admin interface.Affected if Installed version is 1.7.2 or earlier
-
Confirm web interface exposureDetermine if the VikBooking web interface is publicly accessible or accessible to untrusted users via HTTP/HTTPS requests.Affected if The application is exposed to untrusted networks or users
-
Review access control configurationInspect the access control settings in the VikBooking admin panel under user permissions, access levels, or security settings. Verify that role-based access controls are properly defined.Affected if Access control settings are missing, misconfigured, or allow overly permissive user roles
-
Check for unauthorized access indicatorsReview application logs, access logs, and audit trails for unusual access patterns, privilege escalation attempts, or actions performed by users beyond their assigned roles.Affected if Logs show access attempts or actions performed outside assigned user privileges
-
Verify sensitive endpoint protectionTest access to sensitive administrative functions, booking management, customer data, and configuration pages using an unprivileged or unauthenticated account.Affected if Unprivileged or unauthenticated users can access sensitive endpoints or perform administrative actions
You are affected if VikBooking version 1.7.2 or earlier is installed and exposed, especially if access control is misconfigured or allows unauthorized access to sensitive functions.
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 proper authorization checks on all sensitive endpoints and functions, enforce role-based access control (RBAC) consistently across the application, and verify the fix against the OWASP Access Control Cheat Sheet.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22670 — 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-2025-22670 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