CVE-2025-58690
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 ptibogxiv Doliconnect doliconnect allows Stored XSS.This issue affects Doliconnect: from n/a through <= 9.5.7.
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 Doliconnect allows attackers to craft malicious requests that result in Stored XSS. The lack of anti-CSRF tokens on forms enables attackers to trick authenticated users into submitting requests that inject malicious scripts into the application, which then executes when other users view the stored content.
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 Doliconnect installationCheck for Doliconnect by locating its main PHP files (e.g., doliconnect.php) or the application directory in your webroot. Look for folders named 'doliconnect' or files containing 'doliconnect' in the filename.Affected if Doliconnect software is found on the system
-
Determine installed Doliconnect versionLocate the version file or check the admin dashboard for the Doliconnect version number. Common locations include a 'version.php' file, a 'readme' file, or the administration panel under 'About' or 'System Info'.Affected if The installed version does not include the CVE-2025-58690 fix or the version cannot be determined
-
Inspect forms for anti-CSRF tokensView the HTML source of state-changing forms (e.g., forms that submit user input, update settings, or create content). Look for hidden input fields with names like 'csrf_token', 'nonce', 'token', 'csrf', 'xsrf', or similar security token identifiers.Affected if Forms lack hidden token fields or the tokens are not validated server-side
-
Verify token validation server-sideReview the PHP source code that handles form submissions. Check if the form handler validates the presence and correctness of anti-CSRF tokens before processing any state-changing request.Affected if Form handlers do not validate anti-CSRF tokens or skip validation entirely
-
Test for Stored XSS via CSRFUsing an authenticated session, submit a form with a test script payload (e.g., <script>alert('XSS')</script>) without any anti-CSRF token. Then navigate to the page where the content is displayed to see if the script executes.Affected if The malicious script executes when viewing the stored content, indicating both CSRF and Stored XSS are present
You are affected if Doliconnect is installed and its forms lack anti-CSRF token protection, allowing authenticated users to be tricked into injecting malicious scripts that execute for other 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 anti-CSRF tokens on all state-changing forms and endpoints, combined with proper input validation and output encoding to prevent Stored XSS execution.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58690 — 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-58690 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