dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-10947

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A flaw has been found in Sistemas Pleno Gestão de Locação up to 2025.7.x. The impacted element is an unknown function of the file /api/areacliente/pessoa/validarCpf of the component CPF Handler. Executing a manipulation of the argument pes_cpf can lead to authorization bypass. The attack can be executed remotely. The exploit has been published and may be used. Upgrading to version 2025.8.0 is sufficient to resolve this issue. It is advisable to upgrade the affected component.

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 · moderate confidence

The vulnerability exists in the CPF validation endpoint (/api/areacliente/pessoa/validarCpf) of Sistemas Pleno Gestão de Locação. By manipulating the pes_cpf argument, an attacker can bypass authorization checks. This is a classic IDOR (Insecure Direct Object Reference) or broken access control issue in the API's CPF handler component.

MitigationUpgrade to version 2025.8.0 as the vendor has indicated this version contains the fix. After upgrading, verify that the /api/areacliente/pessoa/validarCpf endpoint properly enforces authorization checks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 installed version of Sistemas Pleno Gestão de Locação
    Locate the software version information in the application administrative panel, system configuration files, or by querying the application's /api/version endpoint if available. Compare the version number to the fixed release 2025.8.0.
    Affected if Version is before 2025.8.0 or the version cannot be determined.
  2. Confirm endpoint existence and accessibility
    Send an HTTP request to the path /api/areacliente/pessoa/validarCpf and observe whether the endpoint responds (even with an error). The endpoint should not be publicly accessible without proper authorization.
    Affected if The endpoint returns any HTTP response (including 401, 403, 404, or 200) indicating the endpoint exists and is reachable.
  3. Test for authorization bypass via pes_cpf parameter
    Make an authenticated request to the endpoint using one valid CPF, then repeat the request with a different pes_cpf value belonging to another user. Observe if the application returns data or validation results for the alternate CPF without proper authorization checks.
    Affected if The application accepts and processes requests with an arbitrary pes_cpf value, returning validation results for any CPF regardless of ownership.
  4. Verify if the IDOR condition is exploitable
    Submit sequential requests to /api/areacliente/pessoa/validarCpf with different pes_cpf values while using an authenticated session. Check whether the responses differ or leak information about CPFs that do not belong to the authenticated user.
    Affected if The endpoint returns different results for different pes_cpf values without enforcing that the authenticated user owns or is authorized to query the specific CPF.

A system is affected if it runs Sistemas Pleno Gestão de Locação before version 2025.8.0 and the /api/areacliente/pessoa/validarCpf endpoint is accessible and allows unauthorized access to arbitrary CPF data via parameter manipulation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2025.8.0 as the vendor has indicated this version contains the fix. After upgrading, verify that the /api/areacliente/pessoa/validarCpf endpoint properly enforces authorization checks.

Recommended fix High confidence

2025.8.0

  1. 1. Create a complete backup of the current Sistemas Pleno Gestão de Locação installation, including database and configuration files.
  2. 2. Verify the current installed version is 2025.7.x or earlier.
  3. 3. Obtain the patched version 2025.8.0 from the official vendor distribution channel.
  4. 4. Apply the upgrade to the production environment following standard vendor upgrade procedures.
  5. 5. Verify the upgrade was successful by checking the application version.
  6. 6. Test the /api/areacliente/pessoa/validarCpf endpoint to confirm the authorization bypass is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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