CVE-2025-67634
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 · uneditedThe CISA Software Acquisition Guide Supplier Response Web Tool before 2025-12-11 was vulnerable to cross-site scripting via text fields. If an attacker could convince a user to import a specially-crafted JSON file, the Tool would load JavaScript from the file into the page. The JavaScript would execute in the context of the user's browser when the user submits the page (clicks 'Next').
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 confidenceThe CISA Software Acquisition Guide Supplier Response Web Tool does not sanitize text fields from imported JSON files before rendering them in the page. When a user imports a malicious JSON file containing XSS payloads in text fields, the embedded JavaScript executes in the user's browser context upon page submission (clicking 'Next').
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-12-11CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the installed version of CISA Software Acquisition GuideCheck the application web interface, typically found in the footer, About page, or Help section for the software version numberAffected if The version is displayed as a date earlier than 2025-12-11 or shows no version date at all (unpatched)
-
Determine if the JSON import feature has been usedReview application logs, session history, or browser local storage for evidence of JSON file imports. Look for any imported supplier response filesAffected if JSON import functionality has been used to bring data into the tool
-
Inspect any imported JSON files for potential XSS payloadsLocate and examine any JSON files that were imported into the tool. Check text field values for suspicious patterns like <script>, javascript:, onerror=, or other HTML/JavaScript syntaxAffected if Any imported JSON files contain XSS payload patterns in text fields that would execute upon page submission
-
Test for XSS vulnerability in current environmentCreate a test JSON file with a benign XSS probe in a text field (e.g., a text field containing <img src=x onerror=alert(1)>), import it into the tool, and click Next to see if the script executesAffected if The imported XSS payload executes in the browser context when clicking Next after import (perform this test only in a non-production environment)
-
Review browser developer console for script errors or executionOpen browser developer tools (F12), go to Console tab, then import a JSON file and click Next. Monitor for any script execution or errorsAffected if JavaScript code from imported JSON text fields executes or attempts to execute without sanitization
A user is affected if they are running a version of CISA Software Acquisition Guide dated before 2025-12-11 AND have imported JSON files containing untrusted or potentially malicious text field content.
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.
dbcve · scoped2025-12-11
Update to the patched version released on or after 2025-12-11 which implements proper input validation and output encoding for JSON-imported text fields.
2025-12-11 or later
- Obtain the updated CISA Software Acquisition Guide Supplier Response Web Tool version 2025-12-11 or later from the official CISA repository
- Back up any existing configuration, data, or customizations from the current installation
- Install or deploy the updated version (2025-12-11 or later) following standard deployment procedures
- Verify the fix is applied by attempting to import a test JSON file with script content - the application should now sanitize or reject the malicious input
- Confirm the 'Next' button functionality works correctly with normal, legitimate JSON imports
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67634 — 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-67634 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