dbcve.org
PetlibroApplication

CVE-2025-3660

HIGH · 8.2 CVSS v3.1 Published 2026-01-04
Fix available
A fix is available. Upgrade to after 1.7.31 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Petlibro Smart Pet Feeder Platform versions up to 1.7.31 contains a broken access control vulnerability that allows authenticated users to access other users' pet data by exploiting missing ownership verification. Attackers can send requests to /member/pet/detailV2 with arbitrary pet IDs to retrieve sensitive information including pet details, member IDs, and avatar URLs 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 confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Petlibro Smart Pet Feeder Platform's /member/pet/detailV2 endpoint. Authenticated users can access other users' pet data by supplying arbitrary pet IDs without any ownership verification, exposing sensitive information including pet details, member IDs, and avatar URLs.

MitigationImplement proper authorization checks at the /member/pet/detailV2 endpoint (and audit similar endpoints) to verify that the authenticated user owns or has permission to access the requested pet resource before returning any data.

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
PetlibroApplication
Affected:<= 1.7.31

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Petlibro platform version
    Locate the installed Petlibro Smart Pet Feeder Platform version number through the application UI settings, about page, or API response headers. Common locations include the mobile app settings menu, device firmware information, or API /version endpoint.
    Affected if The installed version is 1.7.31 or any version up to 1.7.31 (any version <= 1.7.31)
  2. Verify /member/pet/detailV2 endpoint exists
    Send an authenticated HTTP GET request to the /member/pet/detailV2 endpoint using valid user credentials. Capture the HTTP response to confirm the endpoint is accessible and responds to requests.
    Affected if The endpoint responds with HTTP 200 and returns pet data, indicating the feature is enabled
  3. Test for IDOR via pet ID manipulation
    After authenticating with valid credentials, make a request to /member/pet/detailV2 with a pet ID parameter that does not belong to the authenticated user. Compare the response to determine if pet data from another user is returned without authorization errors.
    Affected if The endpoint returns pet data (pet details, member IDs, avatar URLs) for a pet ID that does not belong to the requesting user, indicating missing ownership verification
  4. Inspect request/response for authorization headers
    Examine HTTP request headers and API responses for proper authorization tokens and verify that the response does not contain Cross-Origin Resource Sharing (CORS) misconfigurations that could allow unauthorized cross-user access.
    Affected if No ownership verification is performed server-side before returning pet data, or the response includes data from other users' pets

A user is affected if they are running Petlibro platform version 1.7.31 or any prior version, and the /member/pet/detailV2 endpoint returns pet data belonging to other users when manipulating the pet ID parameter.

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.

From vendor data
Upgrade available Upgrade to a release after 1.7.31
Interim mitigation

Implement proper authorization checks at the /member/pet/detailV2 endpoint (and audit similar endpoints) to verify that the authenticated user owns or has permission to access the requested pet resource before returning any data.

Fix this in Petlibro 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-3660 — 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-3660 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