CVE-2025-62956
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 iseremet Reloadly reloadly-topup-widget allows Stored XSS.This issue affects Reloadly: from n/a through <= 2.0.1.
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 the reloadly-topup-widget enables attackers to trick authenticated users into submitting requests that store malicious XSS payloads. The lack of CSRF protection allows cross-site request forgery, which can lead to stored cross-site scripting when malicious scripts are persisted in the application.
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 reloadly-topup-widget is presentSearch your codebase, dependencies, or installed packages for 'reloadly-topup-widget' or similar namingAffected if The widget is present in your environment
-
Determine the widget versionCheck your package.json, composer.json, or dependency lock file for the installed version of the reloadly-topup-widgetAffected if The installed version has known CSRF protection gaps (compare to any published fixed version if available)
-
Verify authentication is required for widget operationsExamine the application's authentication layer to confirm users must be logged in before interacting with the widgetAffected if The widget allows unauthenticated state-changing requests
-
Inspect API endpoints for anti-CSRF tokensReview the network requests made by the widget; check if POST/PUT/DELETE requests include anti-CSRF tokens or SameSite cookiesAffected if State-changing requests lack anti-CSRF token validation
-
Test for origin validation on state-changing operationsUse browser developer tools to inspect request headers; verify the Origin or Referer header is validated server-side before processing requestsAffected if The server accepts requests without validating the request origin
-
Check if input sanitization prevents stored XSSSubmit a test XSS payload through the widget and verify if it gets stored and executed without sanitizationAffected if Malicious scripts can be persisted and rendered without encoding
You are affected if you use the reloadly-topup-widget without proper anti-CSRF token validation on state-changing endpoints, which allows attackers to store malicious XSS payloads via tricked authenticated 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 and proper origin validation for all state-changing operations, combined with output encoding and input sanitization to prevent stored XSS.
- 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-62956 — 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-62956 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