PatchSiren cyber security CVE debrief
CVE-2025-3660 Petlibro CVE debrief
The CVE record for CVE-2025-3660 was published on 2026-01-04T00:15:44.433Z and has not been modified since then. The NVD entry is currently Analyzed. This broken access control vulnerability in Petlibro Smart Pet Feeder Platform versions up to 1.7.31 allows authenticated users to access other users' pet data by exploiting missing ownership verification. The vulnerability has a CVSS score of 6.9 and is classified as MEDIUM severity. Users of the platform should be aware of this vulnerability and take necessary precautions.
- Vendor
- Petlibro
- Product
- Smart Pet Feeder Platform
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-01-04
- Original CVE updated
- 2026-07-20
- Advisory published
- 2026-01-04
- Advisory updated
- 2026-07-20
Who should care
Users of Petlibro Smart Pet Feeder Platform versions up to 1.7.31 should be aware of this broken access control vulnerability. Operators of the platform, vulnerability management teams, and security teams should review the official advisory and CVE record for affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Technical summary
CVE-2025-3660 is a broken access control vulnerability in Petlibro Smart Pet Feeder Platform versions up to 1.7.31. Authenticated users can access other users' pet data by exploiting missing ownership verification, allowing retrieval of sensitive information including pet details, member IDs, and avatar URLs. The vulnerability has a CVSS score of 6.9 and is classified as MEDIUM severity. Users of the platform should verify and limit access to the /member/pet/detailV2 endpoint and implement proper authorization checks for pet data retrieval.
Defensive priority
Medium priority due to CVSS score of 6.9 and potential for sensitive information disclosure.
Recommended defensive actions
- Verify and limit access to the /member/pet/detailV2 endpoint
- Implement proper authorization checks for pet data retrieval
- Update Petlibro Smart Pet Feeder Platform to version above 1.7.31 if available
- Monitor for suspicious activity related to pet data access
- Conduct regular security audits and penetration testing
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD detail provide information about the vulnerability. Limited additional information is available from the source item and references. Evidence limits suggest verifying the Petlibro Smart Pet Feeder Platform versions up to 1.7.31 for potential exposure. Defenders should review the official advisory and CVE record for affected scope, severity, and vendor guidance. They should also monitor for suspicious activity related to pet data access and conduct regular security audits and penetration testing.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-3660 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-3660
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-3660 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-3660
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://bobdahacker.com/blog/petlibro
[email protected] - Product
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/petlibro-smart-pet-feeder-platform-through-broken-access-control-via-api-endpoint
[email protected] - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.