Skip to content
KitploitKITPLOIT
ToolsBlog
Log in
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-78071 — Stored XSS via Location Title in DPCalendar Free | Kitploit
Tools/GitHubGitHub/toanln-cov/cve-2026-78071
Vulnerability AnalysisCode AnalysisExploitationWeb Application ExploitationWeb Security
GitHubtoanln-cov/cve-2026-78071

CVE-2026-78071

Stored XSS via Location Title in DPCalendar Free

View Repository
222 months agoNot yet reviewed
Share

Stored XSS via Location Title in DPCalendar Free

DPCalendar Free ≤ 10.11.2 — Author-Role User Bypasses Content Review to Inject Persistent XSS via Location Title, Triggered on Hover by Any Visitor

CVE CVSS CWE-79 Affected Researcher


SUMMARY

The $location->title field is rendered without htmlspecialchars() in default_locations.php. Joomla's server-side InputFilter::clean() strips < and > from string fields but permits ", allowing an Author-role user to break out of an HTML attribute context. When any visitor hovers over the Location information section of an event page, the injected onmouseover handler executes arbitrary JavaScript in their browser session.

A second design flaw amplifies the impact: EventController::allowEdit() checks only created_by == current_user — it does not check event publication state. An Author can create a benign event, have an administrator publish it, and then silently weaponize the linked location by editing its title after publication, bypassing content review entirely. The XSS payload is inserted after moderation; administrators never see it during their review cycle.


AFFECTED VERSIONS

COMPONENTVULNERABLETESTED ONFIXED
DPCalendar Free≤ 10.11.2Joomla 6.1.2 + DPCalendar Free 10.11.2 (PHP 8.3 / Apache)10.12.0

VULNERABILITY DETAILS

Type: Stored Cross-Site Scripting / Improper Output Encoding (CWE-79) Authentication required: Author role — frontend user (Joomla group 4, minimum to create events) File: site/tmpl/event/default_locations.php

Root Cause

$location->title is echoed directly — without htmlspecialchars() — in two output contexts in default_locations.php. The attribute context is the exploitable sink via the web UI, as Joomla's InputFilter blocks <> but passes " through unaltered.

DEFAULT_LOCATIONS.PHP — VULNERABLE OUTPUT SINKS

// Sink 1 — text content (HTML injection; <> stripped by InputFilter via web UI)
<span class="dp-location__title"><?php echo $location->title; ?></span>

// Sink 2 — HTML attribute (attribute injection; " passes through InputFilter)
<div class="dp-location__details"
     data-title="<?php echo $location->title; ?>"

A title value of New Location" onmouseover="alert(document.domain) is stored intact by the server. On output, Sink 2 renders as:

<div class="dp-location__details"
     data-title="New Location" onmouseover="alert(document.domain)"

The onmouseover attribute becomes a live event handler in the rendered DOM.

Missing Publication-State Check

EventController::allowEdit() grants edit access to any Author for their own events regardless of publication state. An attacker establishes trust by submitting a normal event for admin review, then — after publication by admin — silently edits the linked location to inject the XSS payload:

SITE/SRC/CONTROLLER/EVENTCONTROLLER.PHP — ALLOWEDIT() MISSING STATE CHECK

protected function allowEdit($data = [], $key = 'id')
{
    // ...
    return $calendar instanceof CalendarInterface &&
           ($calendar->canEdit() ||
            ($calendar->canEditOwn() &&
             $event->created_by == $this->getCurrentUser()->id));
    // ↑ No check on $event->state — published events remain editable by Author
}

PROOF OF CONCEPT

1. Log in as Author-role user

Navigate to the frontend login form and log in with an Author account (Joomla group 4 — minimum required to create events and locations).

Step 1 — Login as Author

2. Create a normal event with a legitimate location

Navigate to /index.php?option=com_dpcalendar&view=form. Create an event with a clean title and attach any existing location (e.g. "Greater London"). This establishes the Author's legitimacy before the payload is introduced.

Step 2 — Create benign event form

Step 3 — Attach legitimate location before saving

3. Wait for an administrator to publish the event

The event is submitted for review. An administrator logs in and publishes it from the DPCalendar backend. The event is now live and visible to all site visitors.

Step 4 — Admin publishes the event

4. Return to the published event and open the location for editing

As the Author, navigate to the published event page. The Edit Event button remains visible — allowEdit() does not check publication state. Click Edit Event, go to the Location tab, and click the pencil icon to open locationform.

Step 5 — Edit icon still available after admin publish

5. Inject the XSS payload into the Location title field

Replace the location name with the payload. Joomla's InputFilter passes " through — the payload saves intact and breaks the HTML attribute context on output:

PAYLOAD — TITLE FIELD (LOCATIONFORM)

New Location" onmouseover="alert(document.domain)

Step 6 — Inject XSS payload in location title field

Click Save.

6. Any visitor to the event page triggers XSS on hover

When any user — authenticated or anonymous — visits the event detail page and moves their cursor over the Location information section, the injected onmouseover handler fires immediately. No authentication, no click, and no further interaction is required beyond visiting the page.

Step 7 — XSS triggers on hover

The raw payload is visible in the Location section of the event page — the unescaped title is rendered as a live HTML attribute:

Step 8 — Event page showing unescaped payload in DOM

Hovering over the Location section fires the alert dialog in the anonymous visitor's browser:

Step 9 — XSS alert dialog fired for anonymous visitor


IMPACT

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    871
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    548
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    383
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    361
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    305
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →