CVE-2025-6089
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 has been found in Astun Technology iShare Maps 5.4.0 and classified as problematic. This vulnerability affects unknown code of the file atCheckJS.aspx. The manipulation of the argument ref leads to open redirect. The attack can be initiated 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 confidenceAstun Technology iShare Maps 5.4.0 contains an open redirect vulnerability in the atCheckJS.aspx page. The 'ref' parameter is not properly validated before performing a redirect, allowing an attacker to craft a malicious URL that redirects users to an arbitrary site.
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 iShare Maps installationIdentify if Astun Technology iShare Maps is installed in your environment by checking for the application through installed programs, web server content directories, or by accessing the application's web interface.Affected if iShare Maps is not installed in your environment.
-
Check installed versionLocate the version number of your iShare Maps installation. Check the application's About page, footer, or help section. If this is a web application, the version may also be visible in HTTP headers, error pages, or in configuration files within the web root.Affected if The installed version is exactly 5.4.0.
-
Verify atCheckJS.aspx existsAccess the vulnerable page by navigating to the path /atCheckJS.aspx on your iShare Maps web server. For example: http(s)://yourserver/path/to/ishare/atCheckJS.aspxAffected if The atCheckJS.aspx page returns a 200 OK response, indicating it exists and is accessible.
-
Check if 'ref' parameter is acceptedSubmit a test request to atCheckJS.aspx with a 'ref' parameter pointing to an external domain. For example: /atCheckJS.aspx?ref=http://example.com. Observe whether the application performs a redirect based on this parameter.Affected if The application redirects to the URL specified in the 'ref' parameter without validating it, confirming the vulnerability is present.
You are affected if you have Astun Technology iShare Maps version 5.4.0 installed AND the atCheckJS.aspx page is accessible AND it accepts and acts upon an unvalidated 'ref' parameter for redirects.
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 strict validation of the 'ref' parameter to ensure it only allows trusted, relative URLs or a whitelist of allowed domains before performing any redirect.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6089 — 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-6089 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