CVE-2025-3646
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 · uneditedPetlibro Smart Pet Feeder Platform versions up to 1.7.31 contains an authorization bypass vulnerability that allows unauthorized users to add users as shared owners to any device by exploiting missing permission checks. Attackers can send requests to the device share API to gain unauthorized access to devices and view owner information without proper authorization validation.
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 · high confidenceThe Petlibro Smart Pet Feeder Platform versions up to 1.7.31 suffers from an authorization bypass vulnerability in the device share API. Attackers can exploit missing permission checks to add themselves as shared owners to any device without proper authorization validation, gaining unauthorized access and the ability to view owner information.
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.7.31CVSS 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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Petlibro platform versionAccess the device administration interface or API and retrieve the installed firmware/software version number. Check the 'About' or 'System Information' section in the web UI, mobile app, or via API call to /api/version or similar endpoint.Affected if The installed version is 1.7.31 or any earlier version (<= 1.7.31)
-
Verify device share API endpoint exposureIdentify if the device share API endpoint (typically /api/device/share or /api/share) is externally accessible. Check API documentation or network configuration to confirm the endpoint is enabled and reachable.Affected if The share API endpoint is exposed and accessible without proper network segmentation
-
Test authorization on share APISend a share modification request (POST to the share endpoint) with an unauthorized or invalid authentication token. Observe whether the API accepts the request without returning an authorization error (401/403).Affected if The API accepts share operations without validating user permissions (returns 200 OK instead of 401/403)
-
Review API access logs for share operationsExamine server or API logs for share-related endpoints. Look for share operations from unauthenticated sources or from users who should not have permission to modify shares.Affected if Logs show share operations succeeded without proper authentication or from unauthorized user IDs
A user is affected if their Petlibro platform version is 1.7.31 or earlier AND the device share API endpoint is accessible without proper authorization validation.
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 dataUpgrade to version 1.7.32 or later which contains the patch for proper authorization validation in the device share API. Until patched, implement network-level access controls and monitor for suspicious share API requests.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3646 — 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-3646 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