CVE-2025-32644
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 IP2Location IP2Location World Clock ip2location-world-clock allows Stored XSS.This issue affects IP2Location World Clock: from n/a through <= 1.1.9.
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 · high confidenceA CSRF vulnerability in the IP2Location World Clock plugin (versions <= 1.1.9) enables attackers to craft malicious requests that inject and store persistent malicious scripts (Stored XSS) into the application. When users view the compromised content, the injected JavaScript executes in their browsers, potentially stealing session cookies, performing actions as the victim, or redirecting users.
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 IP2Location World Clock plugin is installedCheck your application's plugin or extension directory for the IP2Location World Clock plugin, or view the list of installed plugins in your CMS/application admin panelAffected if The plugin appears in your installed plugins list
-
Determine the installed version of the IP2Location World Clock pluginAccess the plugin settings or version information through your application's admin interface, or check the plugin's main file header for a version commentAffected if The displayed version is 1.1.9 or lower
-
Compare your version to the affected rangeIf you retrieved the version number, verify whether it is less than or equal to 1.1.9Affected if The version is 1.1.9 or any earlier version number
-
Confirm state-changing operations lack CSRF protectionReview plugin source code for absence of anti-CSRF tokens (synchronizer token pattern) on forms or AJAX endpoints that modify dataAffected if No anti-CSRF token validation is found in the plugin's request handlers
-
Inspect stored data for unexpected script contentExamine any database tables or configuration files used by the plugin for any stored JavaScript tags or event handlers that were not intentionally addedAffected if Unexpected script tags or HTML with JavaScript event handlers are present in plugin-stored data
You are affected if the IP2Location World Clock plugin is installed with version 1.1.9 or lower and the plugin lacks CSRF token protection on its data-modifying operations.
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 (synchronizer token pattern) on all state-changing operations and apply proper input validation plus output encoding to prevent XSS. Update to a patched version of the plugin if available.
- 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-32644 — 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-32644 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