Easy Quick ContactApplication · Joomboost

CVE-2023-40659

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A reflected XSS vulnerability was discovered in the Easy Quick Contact module for Joomla.

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

A reflected cross-site scripting (XSS) vulnerability exists in the Easy Quick Contact module for Joomla. The vulnerability allows an attacker to inject malicious JavaScript code through unsanitized user input that gets reflected back to the victim within the web page response.

MitigationApply proper input validation and output encoding/escaping to all user-supplied parameters before rendering them in HTML. Use Joomla's built-in filtering methods or appropriate encoding functions to neutralize script execution attempts.

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
Easy Quick ContactApplication
Affected:>= 1.0.0, <= 1.3.0

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
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 checks

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

  1. Confirm Easy Quick Contact module is installed
    In Joomla administrator panel, go to Extensions > Manage and search for 'Easy Quick Contact' or list all installed modules to verify the presence of Joomboost Easy Quick Contact
    Affected if The module is not found in the extensions list (not affected)
  2. Identify the installed module version
    In Extensions > Manage, click on the Easy Quick Contact entry to view its details and version number
    Affected if The version is between 1.0.0 and 1.3.0 inclusive (potentially affected)
  3. Check if the module is published on the site
    In Joomla administrator, go to Extensions > Modules, filter by type 'mod_easyquickcontact' or search for Easy Quick Contact, and check the status column
    Affected if The module shows as Published (enabled on the frontend)
  4. Verify which module positions or menu items use the module
    In Extensions > Modules, open the Easy Quick Contact module and review the 'Position' assignment and 'Menu Assignment' settings to see where it appears
    Affected if The module is assigned to visible frontend pages

The environment is affected if the Joomboost Easy Quick Contact module is installed with version 1.0.0 through 1.3.0 and is published on the frontend, as the XSS flaw exists in unsanitized user input reflection within this version range.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.0
Interim mitigation

Apply proper input validation and output encoding/escaping to all user-supplied parameters before rendering them in HTML. Use Joomla's built-in filtering methods or appropriate encoding functions to neutralize script execution attempts.

Fix this in Easy Quick Contact Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40659 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-40659 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