Security readout for executives and security teams
Plain-English summary
This is a stored cross-site scripting issue reported in the WordPress plugin Contact Form Integrated With Google Maps versions 1.0 through 2.4. If a site uses the affected plugin, malicious script could be stored and later run in a visitor or administrator browser. The source bundle does not provide CVSS, exploit details, or a named fixed version.
Executive priority
Treat as a targeted WordPress hygiene issue unless the plugin is present on public or high-value sites. Prioritize inventory first, because the evidence does not establish active exploitation or severity scoring.
Technical view
CVE-2014-7238 describes stored XSS in Contact Form Integrated With Google Maps 1.0-2.4 for WordPress. The provided data lacks CWE, CVSS vector, authentication requirements, vulnerable parameter details, and remediation version. KEV status is false, and no provided source states active exploitation.
Likely exposure
Exposure is limited to WordPress sites that have Contact Form Integrated With Google Maps versions 1.0 through 2.4 installed. The bundle does not provide install-base data, vulnerable endpoint details, or whether exploitation requires authentication.
Exploitation context
Stored XSS can be business-relevant because attacker-controlled script may persist and execute when affected content is viewed. No provided source confirms public exploitation, weaponized exploit availability, or CISA KEV listing for this CVE.
Researcher notes
The record is sparse. Useful missing details include vulnerable fields, required privileges, affected routes, sanitization failure, fixed version, and proof of exploitation. Avoid assuming broader product impact beyond the named plugin and versions.
Mitigation direction
- Inventory WordPress sites for the plugin and versions 1.0 through 2.4.
- Check vendor or WordPress plugin guidance for fixed, retired, or replacement versions.
- Disable or remove the plugin where it is unnecessary or cannot be safely updated.
- Review affected sites for unexpected stored script content after confirming exposure.
Validation and detection
- Confirm plugin name and version from WordPress administration or asset inventory.
- Compare findings against the CVE and WPVulnDB records.
- Identify whether untrusted users can submit stored content through the plugin.
- Check logs and content records for suspicious submissions or unauthorized changes.
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-2014-7238 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://wpvulndb.com/vulnerabilities/8235CVE 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.