LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10504: The WebDorado "Form Maker by WD" plugin before 1.12.24 for WordPress allows CSV injection.

The WebDorado "Form Maker by WD" plugin before 1.12.24 for WordPress allows CSV injection.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-10504 affects the WordPress “Form Maker by WD” plugin before 1.12.24. Submitted form data can be stored so that exported CSV files contain spreadsheet formulas. Risk depends on someone exporting and opening the CSV in spreadsheet software.

Executive priority

Prioritize remediation where public forms feed operational CSV exports, especially if staff open them in Excel or similar tools. This is not KEV-listed, but public exploit documentation raises urgency above routine backlog.

Technical view

The issue is CSV injection in WebDorado Form Maker by WD before 1.12.24. The CVE record does not provide CVSS, CWE, or detailed affected CPE data. Exploit-DB has a public entry, but the supplied sources do not show active exploitation.

Likely exposure

Exposure is likely limited to WordPress sites using Form Maker by WD versions older than 1.12.24 and workflows that export submissions to CSV for spreadsheet review.

Exploitation context

The public source bundle references an Exploit-DB entry, so proof-of-concept information exists. KEV is false, and no cited source here confirms active exploitation in the wild.

Researcher notes

The supplied CVE data is sparse: no CVSS, CWE, CPE, exploit maturity detail, or vendor advisory text is included. Treat version confirmation and vendor changelog review as necessary before final exposure decisions.

Mitigation direction

  • Inventory WordPress sites for Form Maker by WD installations.
  • Upgrade affected plugin versions to 1.12.24 or later.
  • Check vendor plugin guidance and changelog before production rollout.
  • Warn staff not to open untrusted CSV exports in spreadsheet software.
  • Review historical CSV exports from affected forms if sensitive workflows used them.

Validation and detection

  • Confirm the plugin name and installed version on each WordPress site.
  • Verify no installed instance is older than 1.12.24.
  • Review form-export workflows that generate CSV files.
  • Check whether submission fields are sanitized before CSV export.
  • Look for prior handling of exported CSV files from public forms.
Prepared
Confidence
medium
Sources
4

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-10504 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
3Source 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.