LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10309: The Responsive Cookie Consent plugin before 1.8 for WordPress mishandles number fields, leading to XSS.

The Responsive Cookie Consent plugin before 1.8 for WordPress mishandles number fields, leading to XSS.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress cookie-consent plugin version before 1.8 had an XSS flaw caused by unsafe handling of number fields. Affected sites could allow malicious script execution in a victim's browser, depending on how the vulnerable fields are reached. The source bundle does not provide CVSS, confirmed active exploitation, or detailed prerequisites.

Executive priority

Prioritize remediation during normal vulnerability patching, faster for public-facing or high-traffic WordPress sites. The issue has public exploit references, but no provided evidence of active exploitation or severity scoring.

Technical view

CVE-2018-10309 affects Responsive Cookie Consent for WordPress before 1.8. The CVE description states that mishandled number fields lead to cross-site scripting. Public references include Exploit-DB and a gist, indicating exploit information exists, but the bundle does not establish active exploitation, authentication requirements, or affected execution context.

Likely exposure

Exposure is limited to WordPress sites running Responsive Cookie Consent before version 1.8. Sites not using this plugin, or already on 1.8 or later, are not indicated as affected by the provided sources.

Exploitation context

The source bundle references public exploit material, including Exploit-DB, but CISA KEV status is false and no cited source states active exploitation. Treat this as publicly documented but not confirmed as exploited in the wild from the provided evidence.

Researcher notes

Evidence is sparse. The CVE identifies XSS via number-field mishandling in versions before 1.8, but does not provide CVSS, CWE, privileges required, user interaction, or storage/reflection details in the bundle. Avoid assuming exploitability conditions without reviewing vendor and reference details.

Mitigation direction

  • Identify WordPress sites using Responsive Cookie Consent.
  • Upgrade the plugin to version 1.8 or later if still installed.
  • Remove the plugin where it is no longer required.
  • Check current vendor guidance before applying compensating controls.

Validation and detection

  • Confirm installed plugin versions across WordPress assets.
  • Flag any Responsive Cookie Consent version earlier than 1.8.
  • Review plugin changelog or deployment history for upgrade confirmation.
  • Check web logs for suspicious activity around plugin-managed fields.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-10309 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.