CVE-2025-22325
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 nchankov Autocompleter autocompleter allows Stored XSS.This issue affects Autocompleter: from n/a through <= 1.3.5.2.
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 the nchankov Autocompleter component allows authenticated users to be tricked into unknowingly submitting requests that inject malicious JavaScript code, resulting in Stored XSS. The lack of anti-CSRF token validation on state-changing operations enables attackers to craft malicious autocomplete entries that persist malicious scripts.
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 nchankov Autocompleter presenceSearch your codebase for files or modules named 'autocompleter', 'Autocompleter', or references to 'nchankov'. Check your dependency manifest (e.g., package.json, composer.json, Gemfile) for the autocompleter component.Affected if The nchankov Autocompleter component is found in your dependencies or codebase.
-
Review autocompleter state-changing endpointsIdentify all API endpoints or functions that accept user input to create, update, or delete autocomplete entries. Examine the request handlers for these state-changing operations.Affected if State-changing operations exist in the autocompleter functionality.
-
Verify anti-CSRF token implementationInspect the state-changing operations identified in step 2. Check whether each operation validates an anti-CSRF token, session token, or other request validation mechanism before processing the request.Affected if No anti-CSRF token validation is found on the autocompleter state-changing operations.
-
Inspect input handling in autocompleterExamine how the autocompleter processes and stores user-supplied input. Look at the data storage layer to see if input is stored as-is or sanitized before persistence.Affected if User input is stored without sanitization or encoding, allowing raw JavaScript or script tags to persist.
You are affected if your environment includes the nchankov Autocompleter component AND its state-changing operations lack anti-CSRF token validation AND user input is stored without proper sanitization, enabling stored XSS injection.
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 operations and add proper input validation/output encoding to prevent stored XSS injection through the autocompleter functionality.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22325 — 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-22325 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