CVE-2025-3654
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 information disclosure vulnerability that allows unauthorized access to device hardware information by exploiting insecure API endpoints. Attackers can retrieve device serial numbers and MAC addresses through /device/devicePetRelation/getBoundDevices using pet IDs, enabling full device control without proper authorization checks.
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 up to version 1.7.31 exposes an unauthenticated API endpoint at /device/devicePetRelation/getBoundDevices that returns device serial numbers and MAC addresses when provided with pet IDs. This broken access control allows attackers to harvest device hardware information and gain full device control without any authorization checks.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Petlibro Feeder Platform installationLocate the Petlibro Smart Pet Feeder Platform software or firmware version running in your environment. Check the application version in the system settings, firmware version on the device, or the deployed software package version.Affected if The installed version is Petlibro Petlibro at version 1.7.31 or any earlier version.
-
Verify API endpoint exposureIdentify if the web API endpoint /device/devicePetRelation/getBoundDevices is accessible in your deployment. Check your API gateway, web server configuration, or network exposure settings for this specific path.Affected if The endpoint is exposed and reachable from your network.
-
Test endpoint authentication requirementAttempt to access the /device/devicePetRelation/getBoundDevices endpoint without providing valid authentication credentials (such as a session token, API key, or login cookie). Use a tool like curl or a web browser to send a request to this endpoint.Affected if The endpoint returns a successful response without requiring authentication.
-
Check for sensitive data exposureSend a request to the endpoint with various pet ID values (even arbitrary or test values) and examine the response payload for the presence of device serial numbers, MAC addresses, or other hardware identifiers.Affected if The endpoint returns device serial numbers or MAC addresses in the response, exposing sensitive hardware information without authorization.
Your environment is affected if you are running Petlibro Smart Pet Feeder Platform version 1.7.31 or earlier and the /device/devicePetRelation/getBoundDevices API endpoint is accessible without authentication and returns device serial numbers or MAC addresses.
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 authentication and authorization validation on the /device/devicePetRelation/getBoundDevices endpoint and audit other API endpoints for similar broken access control vulnerabilities.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3654 — 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-3654 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