dbcve.org
AthocApplication · Blackberry

CVE-2023-21523

MEDIUM · 5.4 CVSS v3.1 Published 2023-09-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Stored Cross-site Scripting (XSS) vulnerability in the Management Console (User Management and Alerts) of BlackBerry AtHoc version 7.15 could allow an attacker to execute script commands in the context of the affected user account.

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 · high confidence

A stored Cross-site Scripting (XSS) vulnerability exists in the User Management and Alerts modules of the BlackBerry AtHoc version 7.15 Management Console. Attackers can inject malicious scripts that execute in the context of the affected user's session, potentially allowing session hijacking, credential theft, or unauthorized actions within the application.

MitigationApply vendor-supplied patch for BlackBerry AtHoc 7.15; implement output encoding and input validation for all user-supplied data in the affected modules; consider implementing Content Security Policy (CSP) headers as defense-in-depth.

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
AthocApplication
Affected:= 7.15

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 BlackBerry AtHoc is deployed
    Review your software inventory or check system information for the presence of BlackBerry AtHoc applications. Look for AtHoc-related services, binaries, or installation directories on the server.
    Affected if BlackBerry AtHoc is not present in the environment, the system is not affected.
  2. Identify the AtHoc version number
    Access the BlackBerry AtHoc Management Console login page or check the application About/Help section. Alternatively, check installation logs, registry entries, or the version property of the AtHoc application binaries.
    Affected if The installed version is exactly 7.15. The vulnerability applies only to this specific version.
  3. Verify Management Console access
    Confirm the Management Console web interface is accessible via browser or API. Check if the console URL (typically /athoc/console or similar) responds.
    Affected if The Management Console is not accessible or not in use, the vulnerability cannot be exploited.
  4. Check User Management module usage
    Log into the Management Console and navigate to the User Management module. Review user account creation, editing, or profile fields for any unexpected or suspicious JavaScript code, HTML tags, or encoded payloads in user-supplied fields.
    Affected if Malicious scripts are present in user records, user profiles, or user-created content within the User Management module.
  5. Check Alerts module usage
    Navigate to the Alerts module in the Management Console. Inspect alert definitions, alert messages, notification templates, or distribution lists for any injected script content.
    Affected if Malicious scripts are found embedded in alert titles, messages, templates, or alert-related metadata.

The environment is affected if BlackBerry AtHoc version 7.15 is running, the Management Console is accessible, and the User Management or Alerts modules contain injected malicious scripts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch for BlackBerry AtHoc 7.15; implement output encoding and input validation for all user-supplied data in the affected modules; consider implementing Content Security Policy (CSP) headers as defense-in-depth.

Fix this in Athoc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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