CVE-2025-30621
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 kornelly Translator translator allows Stored XSS.This issue affects Translator: from n/a through <= 0.3.
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 confidenceCSRF vulnerability in kornelly Translator allows authenticated attackers to craft malicious requests that inject and store XSS payloads. When other users access the affected functionality, the stored malicious scripts execute in their browsers, compromising session tokens or performing actions on behalf of victims.
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 if kornelly Translator is presentCheck installed applications or services for kornelly Translator and determine its version number through package manager, service banner, or application interfaceAffected if The product is installed and the version falls within any affected range or is unknown/unspecified
-
Verify CSRF protection on state-changing operationsInspect HTTP requests and forms related to translation input/submission for the presence of anti-CSRF tokens or unique request identifiers. Check if requests include token parameters or headers that validate request originAffected if No anti-CSRF tokens or stateful validation is found on translation submission endpoints
-
Check for SameSite cookie attributesInspect cookies set by the application during authentication using browser dev tools or by intercepting HTTP responses. Look for SameSite attribute on session-related cookiesAffected if Session cookies lack SameSite attribute or have it set to None without Secure flag
-
Inspect input handling for XSS sanitizationSubmit a test payload containing script-safe HTML characters (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) through the translation input field and observe how the input is processed or storedAffected if The application accepts and stores HTML/script content without sanitization or encoding
-
Verify output encoding on affected functionalityAccess the functionality where stored translations are displayed (as another user or in a different session). Use browser dev tools or intercept responses to examine if stored content is rendered with context-aware encodingAffected if Stored content is reflected in the response without proper HTML entity encoding or context-aware escaping, allowing script execution
A user is affected if kornelly Translator is installed, state-changing operations lack CSRF tokens, and input fields accept/stored content without sanitization that executes as script in other users' browsers.
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 with stateful validation on state-changing operations, add SameSite cookie attributes, and apply context-aware output encoding/sanitization to prevent stored XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30621 — 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-30621 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