CVE-2025-52493
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 · uneditedPagerDuty 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.
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 confidenceThis is a DOM-based information disclosure vulnerability where PagerDuty Runbook's configuration page renders secret values directly into the HTML source, even though they appear visually masked as password fields. An attacker with administrative access can trivially reveal these secrets by using browser developer tools to change the input type attribute from 'password' to 'text', exposing stored credentials in plaintext.
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<= 2025-06-12CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PagerDuty Runbook Automation versionCheck the installed version of PagerDuty Runbook Automation through the application admin panel, typically found in Help > About or the system settings pageAffected if The installed version is 2025-06-12 or earlier
-
Navigate to secret configuration areasAccess the configuration or settings pages where credentials, API keys, or other secrets are configured (such as integration settings, credentials management, or connection configurations)Affected if These pages exist and are accessible with administrative privileges
-
Inspect HTML source for secret valuesOpen browser developer tools (F12), go to the Elements tab, and search for input elements with type="password" that contain a value attribute (for example: <input type="password" value="actual-secret-here">)Affected if Secret values are present in the HTML source code even when visually masked as password fields
-
Verify secret exposure via DOM manipulationIn developer tools, locate a password-type input field containing a value, right-click the element, choose Edit as HTML, change type="password" to type="text", and observe whether the plaintext secret becomes visibleAffected if Changing the input type to text reveals the plaintext secret value that was supposedly masked
A user is affected if running PagerDuty Runbook Automation version 2025-06-12 or earlier and the configuration pages expose secret values in the HTML DOM as password-type input fields that can be trivially revealed through browser developer tools.
Generated from the published advisory. Verify against your own configuration.
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 dataThe application should be refactored to never transmit secret values to the client browser. Secrets should be stored server-side and retrieved via secure server-to-server calls only when needed, with proper redaction applied before any data reaches the DOM.
- Consultation4.0 h
- Implementation16.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52493 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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