dbcve.org
PetlibroApplication

CVE-2025-3652

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-04
Fix available
A fix is available. Upgrade to after 1.7.31 or later.
See remediation →
62/100
Remediation priority · Elevated
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 an information disclosure vulnerability that allows unauthorized access to private audio recordings by exploiting sequential audio IDs and insecure assignment endpoints. Attackers can send requests to /device/deviceAudio/use with arbitrary audio IDs to assign recordings to any device, then retrieve audio URLs to access other users' private recordings.

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

The Petlibro Smart Pet Feeder Platform versions up to 1.7.31 contains an Insecure Direct Object Reference (IDOR) vulnerability in the /device/deviceAudio/use endpoint. Attackers can exploit sequential audio IDs to assign arbitrary recordings to any device without authorization, then retrieve the audio URLs to access other users' private recordings. This is a classic broken access control vulnerability where the endpoint lacks proper authorization checks before allowing audio assignment.

MitigationImplement proper authentication and authorization checks on the /device/deviceAudio/use endpoint to verify that the requesting user owns or has permission to access the specific audio resource. Additionally, replace sequential audio IDs with non-predictable identifiers (e.g., UUIDs) and validate user session ownership before returning any audio URLs.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Smart Pet Feeder Platform usage
    Determine if your environment includes the Petlibro Smart Pet Feeder Platform software or service. Check installed applications, IoT device inventories, or network-connected device lists for Petlibro products.
    Affected if The Petlibro Smart Pet Feeder Platform is present in your environment.
  2. Check installed platform version
    Locate the version information for your Petlibro Smart Pet Feeder Platform installation. This may be found in the device settings, mobile app about section, firmware information, or administrative console. Compare the version number to 1.7.31.
    Affected if The installed version is 1.7.31 or any earlier version.
  3. Verify endpoint accessibility
    Identify if the /device/deviceAudio/use API endpoint is exposed and accessible from your network. Check API documentation, network traffic logs, or web application firewall logs for requests to this endpoint.
    Affected if The /device/deviceAudio/use endpoint is reachable from your network.
  4. Test audio ID authorization
    If you have legitimate access to the platform, send a request to /device/deviceAudio/use with an audio ID that you do not own or that belongs to another user. Observe whether the system accepts the request without returning an authorization error.
    Affected if The endpoint accepts and processes audio IDs without validating that the requesting user owns the specified audio recording.

You are affected if you have the Petlibro Smart Pet Feeder Platform running version 1.7.31 or earlier and the /device/deviceAudio/use endpoint accepts audio IDs without proper ownership verification.

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 authentication and authorization checks on the /device/deviceAudio/use endpoint to verify that the requesting user owns or has permission to access the specific audio resource. Additionally, replace sequential audio IDs with non-predictable identifiers (e.g., UUIDs) and validate user session ownership before returning any audio URLs.

Fix this in Petlibro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3652 — 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-3652 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