Zingiri Tickets <= 3.0.3 - Sensitive Information Disclosure
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Support Tickets Center
- Affected Version
<= 3.0.3- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Support Tickets Center WordPress plugin, affecting versions <= 3.0.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2012, reported by MadLeeTs.
Vulnerability Overview
The Zingiri Tickets plugin for WordPress is vulnerable to Sensitive Data Exposure via the 'log.txt' file. This can allow unauthenticated attackers to extract sensitive data including Admin username and/or password hashes.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Support Tickets Center <= 3.0.3 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. No fixed build of this plugin is recorded for Support Tickets Center yet, so installs running <= 3.0.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
No patched version is recorded yet, so there is nothing to update to; WordSec's vulnerability alerts flag this record the moment that changes.
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C