dbcve.org
MapsApplication · Phoca

CVE-2026-23900

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-11
Fix available
A fix is available. Upgrade to after 6.0.2 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Various stored XSS vulnerabilities in the maps- and icon rendering logic in Phoca Maps component 5.0.0-6.0.2 have been discovered.

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 confidence

Stored XSS vulnerabilities exist in the maps- and icon rendering logic of Phoca Maps component versions 5.0.0 through 6.0.2. The vulnerability allows attackers to inject malicious scripts that are persisted on the server and executed when other users view the affected maps or icons.

MitigationUpdate to the latest patched version of Phoca Maps when available. Until then, implement output encoding and input validation on all user-supplied data rendered in maps and icons, and consider restricting map creation permissions to trusted users.

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
MapsApplication
Affected:>= 5.0.0, <= 6.0.2

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Phoca Maps component is installed
    Access Joomla administrator panel, navigate to Components menu and look for Phoca Maps entry, or check for Phoca Maps files in /administrator/components/com_phocamaps/ and /components/com_phocamaps/ directories via file system
    Affected if Phoca Maps component exists in the Joomla installation
  2. Determine installed Phoca Maps version
    In Joomla admin, go to Components > Phoca Maps and look for version information typically displayed in the component header or about page, or inspect the manifest XML file at /administrator/components/com_phocamaps/phocamaps.xml
    Affected if Installed version falls within 5.0.0 through 6.0.2 inclusive
  3. Identify stored maps or icons in the component
    Access Phoca Maps admin panel and review existing maps (typically under Maps or Map Items) and icons (typically under Icons or Markers) that may contain user-supplied titles, descriptions, or custom icon names
    Affected if Any maps or icons exist in the component, especially those created by users with limited trust
  4. Inspect map and icon content for potential XSS payloads
    Review the raw data of stored maps and icons in the database or via admin panel, looking for script tags, event handlers (onclick, onerror, etc.), or other HTML/JavaScript in fields such as title, description, icon path, or marker data
    Affected if Any map or icon entry contains unsanitized HTML or JavaScript code in rendering-relevant fields
  5. Check user permissions for map and icon creation
    Navigate to Joomla Users > Access Levels or Phoca Maps own permission settings to review which user groups can create or edit maps and icons
    Affected if Users outside trusted administrator groups have permission to create or modify maps or icons

A user is affected if Phoca Maps version 5.0.0 through 6.0.2 is installed and maps or icons containing unsanitized user-supplied content exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.0.2
Interim mitigation

Update to the latest patched version of Phoca Maps when available. Until then, implement output encoding and input validation on all user-supplied data rendered in maps and icons, and consider restricting map creation permissions to trusted users.

Recommended fix Moderate confidence

Phoca Maps version > 6.0.3 (check phoca.cz for the latest stable release)

  1. 1. Visit the official Phoca website (phoca.cz) to check for the latest version of Phoca Maps component
  2. 2. Download the most recent stable release that is higher than version 6.0.2
  3. 3. Before upgrading, create a complete backup of your Joomla site including files and database
  4. 4. Install the new version through the Joomla administrator panel under Extensions > Manage > Install
  5. 5. Verify that the XSS vulnerability is resolved by testing map and icon rendering with malicious input payloads
  6. 6. Clear any caching to ensure the new version's templates are loaded
Caveat Review the changelog for any template overrides or configuration changes that may require updates to custom templates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maps Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23900 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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