Simple Ajax ChatWordPress extension · Plugin Planet
CVE-2022-27849
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 · uneditedSensitive Information Disclosure (sac-export.csv) in Simple Ajax Chat (WordPress plugin) <= 20220115
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 confidenceThe Simple Ajax Chat WordPress plugin versions up to 20220115 exposes a sensitive CSV export file (sac-export.csv) that can be accessed directly without authentication, allowing unauthenticated attackers to download chat logs containing potentially sensitive user information such as usernames, IP addresses, message content, and timestamps.
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
Simple Ajax ChatWordPress extension
<= 20220115CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Simple Ajax Chat plugin is installedNavigate to WordPress admin > Plugins and look for 'Simple Ajax Chat' by Plugin Planet in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn WordPress admin > Plugins > Simple Ajax Chat, look for the version number displayed beneath the plugin nameAffected if Version is 20220115 or lower (any version up to and including 20220115)
-
Verify sac-export.csv file existsAccess your web server document root (typically /var/www/html or similar) and check for the file /wp-content/uploads/sac-export.csv, or attempt to access it via URL: https://yourdomain.com/wp-content/uploads/sac-export.csvAffected if The file sac-export.csv exists in the uploads directory and is publicly accessible
-
Confirm unauthenticated access to export fileOpen a private/incognito browser window (not logged into WordPress) and navigate to the suspected path: /wp-content/uploads/sac-export.csv or check plugin settings for export file pathAffected if The CSV file downloads or displays without requiring login credentials, showing chat logs with usernames, IPs, messages, and timestamps
If Simple Ajax Chat plugin version 20220115 or lower is installed AND the sac-export.csv file is accessible without authentication, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Simple Ajax Chat plugin to the latest version beyond 20220115 to obtain the security patch. If no patch is available, block direct web access to the sac-export.csv file via .htaccess rules or web server configuration, or disable the plugin until a patched version is released.
Fix this in Simple Ajax Chat
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27849 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27849 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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