PXLSecurity LTD., Sofia, Bulgaria Offensive security since 2014[email protected]

CVE-2024-0405

Burst Statistics for WordPress SQL injection

Post-authenticated SQL injection via multiple JSON parameters in a REST endpoint.

SQL injectionburstbvHigh

Technical summary

Burst Statistics is a privacy-focused analytics plugin for WordPress. Its REST endpoint /wp-json/burst/v1/data/compare accepts several JSON parameters — the record names browser, device, page_id, page_url, platform and referrer — and uses them in SQL without neutralising them.

The two published scores disagree on the bar: Wordfence puts privileges required at high and scores 7.2, while NVD puts it at low with confidentiality-only impact and scores 6.5. Both vectors are shown above; we publish them as published rather than picking one.

Impact

An authenticated user can read data from the WordPress database through the analytics endpoint, well beyond the aggregate statistics the endpoint is meant to return.

The Burst Statistics – Privacy-Friendly Analytics for WordPress plugin, version 1.5.3, is vulnerable to Post-Authenticated SQL Injection via multiple JSON parameters in the /wp-json/burst/v1/data/compare endpoint. Affected parameters include 'browser', 'device', 'page_id', 'page_url', 'platform', and 'referrer'.

Remediation

The vendor patch is visible in the plugin’s changeset, linked below. The published record does not name a fixed version number, so none is stated here.

Published severity

Published byVersionBase scoreVector
Wordfence (CNA)CVSS 3.1 7.2 High CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVDCVSS 3.1 6.5 Medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

More than one organisation has scored this issue. We reproduce every published score and vector as published, attributed to its source, and do not compute our own.

Disclosure timeline

  1. 2024-01-05Vendor notified
  2. 2024-01-16Disclosed
  3. 2024-01-17CVE record published

Dates as recorded in the CVE record’s own timeline field. See the record.

References

Credit

Researcher: Ivan Spiridonov

Credited as finder in the CVE record published by Wordfence.

This is the work we do commercially

Vulnerability research and penetration testing by the same engineers who found this issue. Every report carries reproduction steps, impact and a retest.

We publish advisories, not exploits. Each entry describes the vulnerability class and impact at the level the vendor advisory does, and links to the authoritative records. Where public proof-of-concept code exists we link to it rather than reproduce it.

How we disclose

Every issue here was reported to the vendor or to a coordinating programme before publication. We publish only once a fix is available or the coordinated disclosure window has elapsed.

Want this kind of scrutiny on your own software?

Tell us what you want to protect. A senior tester will help you agree the scope and next steps. We usually reply within one business day.

Confidential from the first conversation

We can sign your NDA before you share sensitive details. Your enquiry is covered by our privacy policy.

How we protect your information · Privacy policy