# CVE-2025-52493: Information disclosure in n/a

> Administrative users can reveal stored secrets in the PagerDuty Runbook configuration page by inspecting the DOM, exposing sensitive credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-4545-vgx6-83vr

## What is CVE-2025-52493?

CVE-2025-52493 is a medium-severity vulnerability in n/a, published on 10 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PagerDuty Runbook through 2025-06-12 exposes stored secrets directly in the webpage DOM at the configuration page. Although these secrets appear masked as password fields, the actual secret values are present in the page source and can be revealed by simply modifying the input field type from "password" to "text" using browser developer tools. This vulnerability is exploitable by administrative users who have access to the configuration page.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-52493?

It affects 1 product.


Products: Pagerduty Runbook Automation.

## How do I fix CVE-2025-52493?

No fix has been published for CVE-2025-52493 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52493 being exploited?

There is no known exploitation of CVE-2025-52493 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52493 and fix it if it is affected.

What it is: CVE-2025-52493 is a medium-severity vulnerability in n/a, published on 10 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52493 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52493/ (Markdown: https://insights.sbomify.com/CVE-2025-52493/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52493
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52493
- OSV: https://osv.dev/vulnerability/CVE-2025-52493

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52493/
Summaries are generated and may contain mistakes; the official description above is the record.