Para Inserts Sensitive Information into Log File for Facebook authentication

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2025-49009: 0.17% estimated exploitation activity in the next 30 days; percentile 6.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CWE ID: CWE-532 (Insertion of Sensitive Information into Log File) CVSS: 6.2 (Medium) Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Affected Component: Facebook Authentication Logging Version: Para v1.50.6 File Path: para-1.50.6/para-server/src/main/java/com/erudika/para/server/security/filters/FacebookAuthFilter.java Vulnerable Line(s): Line 184 (logger.warn(...) with raw access token) Technical Details: The vulnerability is located in FacebookAuthFilter.java, where a failed request to Facebook’s user profile endpoint triggers the following log statement: Here, PROFILEURL is a constant: This results in the full request URL being logged, including the user's access token in plain text. Since WARN-level logs are often retained in production and accessible to operators or log aggregation systems, this poses a risk of token exposure.

Published by the source

6 Jun 2025, 15:49 UTC

Last modified by the source

13 Jun 2025, 15:28 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qx7g-fx8q-545g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-49009

Advisory: Para Inserts Sensitive Information into Log File for Facebook authentication
IDs: CVE-2025-49009, GHSA-qx7g-fx8q-545g
Record: https://patchnext.com/advisories/cve-2025-49009 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.erudika:para-server 1.50.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.erudika:para-server: affected < 1.50.8; fixed in 1.50.8

## Suggested inspection (read-only)
- Maven com.erudika:para-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.erudika:para-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qx7g-fx8q-545g (GitHub-reviewed advisory GHSA-qx7g-fx8q-545g lists affected ranges: Maven com.erudika:para-server >=0 <1.50.8)

Commands are suggestions: review each one before running it.