CVE-2025-3653: Petlibro Smart Pet Feeder through 1.7.31 Platform Improper Access Control via API endpoint
Petlibro Smart Pet Feeder Platform versions up to 1.7.31 contains an improper access control vulnerability that allows unauthorized device manipulation by accepting arbitrary serial numbers without ownership verification. Attackers can control any device by sending serial numbers to device control APIs to change feeding schedules, trigger manual feeds, access camera feeds, and modify device settings without authorization checks.
Security readout for executives and security teams
Plain-English summary
This vulnerability means Petlibro cloud controls for smart feeders may trust a device serial number instead of proving account ownership. An unauthenticated attacker could manipulate feeders, schedules, settings, manual feeds, and camera access for devices they do not own. This creates privacy, safety, and trust risk for connected pet care operations.
Executive priority
Treat as a high-priority consumer IoT exposure where privacy and physical-world device behavior are affected. Prioritize confirmation of affected devices and vendor remediation status before continued remote operation.
Technical view
CVE-2025-3653 is improper access control, CWE-612, in Smart Pet Feeder Platform through 1.7.31. Sources state device control APIs accept arbitrary serial numbers without ownership verification. CVSS 3.1 is 7.3 high: network, low complexity, no privileges, no user interaction, with low confidentiality, integrity, and availability impact.
Likely exposure
Likely exposure is users or organizations operating Petlibro smart feeders tied to the affected platform through version 1.7.31. The bundle does not prove whether all models, regions, firmware versions, or cloud tenants are affected.
Exploitation context
The bundle does not cite CISA KEV listing or confirmed active exploitation. Public research and VulnCheck describe unauthenticated unauthorized device manipulation, but operational exploit prevalence is not established in the provided evidence.
Researcher notes
The central issue is missing ownership authorization around serial-number-based device control. Evidence is strong for vulnerability class and impact, but incomplete for fixed versions, exploit activity, affected model scope, and vendor remediation details.
Mitigation direction
Check Petlibro guidance for patched platform, app, firmware, or cloud-side fixes.
Update affected apps, firmware, and devices when vendor-supported fixes are available.
Temporarily disable remote control and camera features where business risk is unacceptable.
Remove unneeded devices from accounts and decommission unused feeders.
Monitor account and device activity for unexpected feeding, camera, or settings changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-612: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-612 · source CWE mapping
Improper Authorization of Index Containing Sensitive Information
Improper Authorization of Index Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.