Security readout for executives and security teams
Plain-English summary
CVE-2025-23932 is a critical vulnerability in the WordPress Quick Count plugin through version 3.00. The issue can allow attacker-controlled object injection through unsafe deserialization. The published score indicates possible full confidentiality, integrity, and availability impact, but the source bundle does not confirm exploitation in the wild.
Executive priority
Treat this as urgent for any public WordPress site using Quick Count. The severity is critical and unauthenticated remote impact is indicated, but current evidence does not confirm active exploitation or a named patch in the provided bundle.
Technical view
The CVE describes CWE-502 deserialization of untrusted data in Marko-M Quick Count, package quick-count, affecting versions through 3.00. CVSS 3.1 is 9.8 with network, low-complexity, unauthenticated, no-user-interaction attack characteristics. Source details do not provide exploit prerequisites beyond object injection or a confirmed patched version.
Likely exposure
Exposure is likely limited to WordPress sites with the Quick Count plugin installed at version 3.00 or earlier, especially internet-facing sites. Sites without this plugin are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source confirms active exploitation. The CVSS vector suggests remote unauthenticated exploitability, but object-injection impact may depend on application context and available PHP classes.
Researcher notes
Key facts are sparse. The source bundle identifies CWE-502 and object injection, but does not include vulnerable code paths, proof of concept, exploitation status, or patch details. Avoid assuming RCE without confirming gadget-chain feasibility in the target environment.
Mitigation direction
- Inventory WordPress sites for the Quick Count plugin.
- Check vendor or Patchstack guidance for a fixed release.
- Disable or remove Quick Count where it is not required.
- Prioritize remediation on public production WordPress sites.
- Monitor WordPress security logs for suspicious plugin activity.
Validation and detection
- Confirm whether quick-count is installed on each WordPress site.
- Record the installed Quick Count version and flag versions <=3.00.
- Verify remediation against vendor or Patchstack guidance.
- Review logs for anomalous requests before and after remediation.
- Recheck CVE and KEV status before closure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-23932 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/quick-count/vulnerability/wordpress-quick-count-plugin-3-00-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.