CVE-2025-23426
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 Request Forgery (CSRF) vulnerability in Binesh Dobhal go Social go-social allows Stored XSS.This issue affects go Social: from n/a through <= 1.0.
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 confidenceA CSRF vulnerability in go-social <= 1.0 allows authenticated users to be tricked into submitting malicious requests that inject stored XSS payloads into the application. When other users view the injected content, the malicious scripts execute in their browsers, potentially compromising sessions or performing actions on their behalf.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 go-social versionLocate the installed version of the go-social application (check go.mod, version flag, or about page)Affected if The installed version is go-social 1.0 or lower
-
Map state-changing operationsIdentify forms, API endpoints, or routes that modify data (POST, PUT, DELETE requests)Affected if The application has functionality that changes state or submits user data
-
Inspect CSRF protectionExamine the application code or intercept requests to check if state-changing operations include anti-CSRF tokens or SameSite cookie attributesAffected if State-changing operations lack CSRF token validation or SameSite cookie protection
-
Trace user input storage and renderingFollow how user-submitted content is stored in the database and then rendered in responses - look for the code that outputs user content to HTMLAffected if User-generated content is stored and displayed without proper sanitization or encoding
-
Confirm combined vulnerabilityVerify that both the CSRF weakness and the lack of input sanitization exist together in the same applicationAffected if The application lacks CSRF protection on state-changing operations AND renders user input without sanitization, allowing stored XSS
A user is affected if running go-social version 1.0 or lower and the application has state-changing operations without CSRF protection combined with unsanitized user input rendering.
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 anti-CSRF tokens for all state-changing operations and sanitize/encode user-generated content before rendering to prevent stored XSS execution.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23426 — 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-23426 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