CVE-2025-22629
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 iNET iNET Webkit inet-webkit allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects iNET Webkit: from n/a through <= 1.2.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 iNET Webkit (inet-webkit) allows attackers to access functionality that is not properly constrained by Access Control Lists (ACLs). This IDOR-type vulnerability in versions up to and including 1.2.2 permits unauthorized users to perform actions or access resources outside their intended permissions.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify if iNET Webkit is installedSearch for inet-webkit components or check installed software packages using system package manager (dpkg, rpm, brew) or review application inventoryAffected if inet-webkit or iNET Webkit is present on the system
-
Determine installed version of inet-webkitRun version check command provided by the product (typically inet-webkit -v, or check package metadata via package manager, or review application manifest files)Affected if Version is 1.2.2 or lower (any version up to and including 1.2.2)
-
Identify if ACL-based access control is configuredReview product configuration files for ACL rules or permission settings. Look for files named acl.conf, permissions.xml, access_control.json, or similar in the product config directoryAffected if ACL configuration files exist and define user or role-based access rules
-
Check for privileged or sensitive function endpointsReview product documentation or enumerate API/service endpoints to identify functions that should require authorization (admin operations, data access, configuration changes)Affected if The product exposes functions that interact with ACL-protected resources or perform privileged operations
-
Test if authorization can be bypassedAttempt to access a protected resource or function without valid credentials or with a low-privilege account, observing whether the request succeeds despite ACL rulesAffected if Requests to ACL-protected functions succeed without proper authorization (IDOR vulnerability is present)
Environment is affected if inet-webkit is installed with version 1.2.2 or lower and the product exposes functionality that relies on ACLs for access control, as unauthorized users may bypass these restrictions.
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 and ACL enforcement at all sensitive function entry points. Validate user permissions before executing any privileged operation and ensure ACL constraints cannot be bypassed.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22629 — 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-22629 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