Security readout for executives and security teams
Plain-English summary
This is a cross-site scripting issue in the WordPress Count per Day plugin before version 3.2.3, tied to search words. A vulnerable site could expose users to browser-side script execution. The sources do not provide CVSS, CWE, active exploitation evidence, or detailed remediation guidance beyond the affected version boundary.
Executive priority
Handle this as an inventory-driven WordPress plugin hygiene item. Prioritize externally reachable WordPress sites and environments where administrators or authenticated users may view plugin search-word data.
Technical view
CVE-2012-6714 states that Count per Day for WordPress before 3.2.3 has XSS via search words. The source bundle does not confirm the exact affected page, required privileges, or trigger conditions. Validation should focus on plugin presence, version, and vendor changelog guidance.
Likely exposure
Exposure is limited to WordPress installations using the Count per Day plugin earlier than 3.2.3. Sites without this plugin, or running 3.2.3 or later, are not indicated as affected by the provided sources.
Exploitation context
The provided bundle shows no CISA KEV listing and no cited source stating active exploitation. Public exploitability details, attack prerequisites, and exploitation scale are not established in the supplied evidence.
Researcher notes
Evidence is sparse. The CVE record gives the affected plugin, version boundary, and XSS vector, but not CVSS, CWE, sink location, privileges, or remediation text. Avoid assuming stored, reflected, or admin-only behavior without further vendor evidence.
Mitigation direction
- Inventory WordPress sites for the Count per Day plugin.
- Upgrade Count per Day to version 3.2.3 or later where present.
- If no supported version exists, remove or replace the plugin.
- Check WordPress plugin guidance before making production changes.
- Review logs for suspicious search-word or plugin-related activity.
Validation and detection
- Confirm whether Count per Day is installed on each WordPress site.
- Record the installed plugin version for each instance.
- Verify upgraded sites report version 3.2.3 or later.
- Review vendor plugin notes for security-related release details.
- Confirm no unsupported copies remain in backup or staging sites.
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.
CVE-2012-6714 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/count-per-day/#developersCVE reference · x_refsource_MISC
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.