CVE-2025-5377
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 · uneditedA vulnerability was found in Astun Technology iShare Maps 5.4.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file historic1.asp. The manipulation of the argument Zoom leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 reflected cross-site scripting (XSS) vulnerability exists in Astun Technology iShare Maps 5.4.0 within the historic1.asp file. The 'Zoom' parameter is not properly sanitized, allowing attackers to inject malicious JavaScript that executes in victim browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.4.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm Astun Technology iShare Maps is installedLook for iShare Maps installation directories or check web server logs for requests to ishare maps endpoints. Common paths may include /ishare/, /maps/, or application directories named 'ishare' or 'ashxun'.Affected if The application is Astun Technology iShare Maps and version is 5.4.0
-
Verify the installed version is 5.4.0Check the application version through the software's about page, admin panel, or version file within the installation directory. Compare against the affected version range.Affected if The installed version is exactly 5.4.0
-
Locate historic1.asp fileSearch the web server filesystem for historic1.asp in the iShare Maps installation directories. Check for the presence of this file within the web root.Affected if The file historic1.asp exists in the iShare Maps web directory
-
Confirm the Zoom parameter is accessibleSend an HTTP GET request to historic1.asp with a Zoom parameter, such as: GET /historic1.asp?Zoom=test. Observe if the parameter value is reflected in the response without sanitization.Affected if The Zoom parameter is reflected in the page output without encoding or sanitization
-
Inspect response for XSS vulnerabilitySubmit a harmless XSS test payload in the Zoom parameter, such as: <script>alert(1)</script> or similar, and check if the script executes or is rendered unescaped in the response HTML.Affected if The Zoom parameter value is rendered in the response without HTML encoding, allowing script injection
A user is affected if they have Astun Technology iShare Maps version 5.4.0 installed with the historic1.asp file accessible and the Zoom parameter reflects user input without sanitization.
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 input validation and output encoding on the Zoom parameter in historic1.asp, and consider deploying a WAF rule to block XSS attack patterns until the vendor patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5377 — 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-5377 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