CVE-2025-29156
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 · uneditedCross Site Scripting vulnerability in petstore v.1.0.7 allows a remote attacker to execute arbitrary code via a crafted script to the /api/v3/pet
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 confidenceCross Site Scripting (XSS) vulnerability in petstore v1.0.7 allows remote attackers to inject malicious scripts through the /api/v3/pet endpoint. The application fails to properly sanitize or validate user input, allowing arbitrary JavaScript execution in the context of other users viewing the affected output.
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= 1.0.7CVSS 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 Swagger Petstore installationLocate the application in your environment - check for petstore-related services, containers, or deployed web applications. Look for any Swagger Petstore instance running.Affected if Swagger Petstore application is present in the environment
-
Determine installed versionCheck the application's version information - typically accessible via the UI, API documentation page, or application startup logs. Compare against the affected version 1.0.7.Affected if The installed version is exactly 1.0.7
-
Verify /api/v3/pet endpoint is accessibleAttempt to access the /api/v3/pet endpoint via HTTP request using curl or a similar tool. Check if the endpoint responds and accepts input.Affected if The /api/v3/pet endpoint is publicly or internally accessible and responds to requests
-
Test for XSS susceptibilitySubmit a benign test payload such as <script>alert(1)</script> through the /api/v3/pet endpoint in the pet name or other input fields. Observe if the payload is reflected unsanitized in the response.Affected if The submitted script payload is reflected in the response without sanitization or encoding
You are affected if you are running Smartbear Swagger Petstore version 1.0.7 and the /api/v3/pet endpoint is accessible and reflects unsanitized input back to users.
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 dataImplement proper input validation and output encoding/sanitization on the /api/v3/pet endpoint to neutralize malicious script payloads. Use context-appropriate escaping and consider implementing Content Security Policy headers.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29156 — 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-29156 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