CVE-2025-3660

6.5 MEDIUM

📋 TL;DR

This CVE describes a broken access control vulnerability in the Petlibro Smart Pet Feeder Platform that allows authenticated users to access other users' pet data by exploiting missing ownership verification. Attackers can retrieve sensitive information including pet details, member IDs, and avatar URLs without proper authorization checks. All users of affected Petlibro Smart Pet Feeder Platform versions are impacted.

💻 Affected Systems

Products:
  • Petlibro Smart Pet Feeder Platform
Versions: up to 1.7.31
Operating Systems: All platforms running the vulnerable software
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all deployments with the vulnerable API endpoint accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Mass data breach exposing all user pet data, member IDs, and avatar URLs, potentially leading to privacy violations, targeted phishing attacks, and reputational damage to Petlibro.

🟠

Likely Case

Unauthorized access to limited pet data by curious or malicious authenticated users, resulting in privacy violations and potential data misuse.

🟢

If Mitigated

Minimal impact with proper access controls preventing unauthorized data access and maintaining user data isolation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is straightforward via API endpoint manipulation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Monitor vendor for updates and apply when released.

🔧 Temporary Workarounds

API Endpoint Access Restriction

all

Restrict access to the vulnerable /member/pet/detailV2 endpoint using network controls or web application firewall rules.

Authentication Enhancement

all

Implement additional session validation and user context verification for all API requests.

🧯 If You Can't Patch

  • Implement strict API rate limiting and monitoring for suspicious access patterns to /member/pet/detailV2 endpoint.
  • Deploy web application firewall with rules to detect and block unauthorized pet ID parameter manipulation.

🔍 How to Verify

Check if Vulnerable:

Test authenticated access to /member/pet/detailV2 endpoint with different pet IDs to verify if unauthorized data access is possible.

Check Version:

Check software version in admin interface or configuration files.

Verify Fix Applied:

Verify that authenticated users can only access their own pet data and receive proper authorization errors for other pet IDs.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authorization attempts for pet data access
  • Unusual pattern of pet ID parameter values in API requests
  • Access to /member/pet/detailV2 with non-sequential pet IDs

Network Indicators:

  • High volume of requests to /member/pet/detailV2 endpoint
  • Requests with manipulated pet ID parameters

SIEM Query:

source="web_server" AND uri="/member/pet/detailV2" AND (pet_id NOT IN authorized_pet_ids OR rapid_pet_id_changes)

🔗 References

📤 Share & Export