Security readout for executives and security teams
Plain-English summary
CVE-2017-6096 is a SQL injection issue in the Mail Masta WordPress plugin 1.0. It affects an admin-side list viewing file and requires authentication to WordPress admin. The main business concern is exposure of WordPress database data on sites still running this old plugin.
Executive priority
Treat this as a targeted cleanup item for legacy WordPress assets, not an internet-wide emergency. Prioritize sites with exposed admin panels, weak admin controls, or business-sensitive WordPress data.
Technical view
The issue affects /inc/lists/view-list.php in Mail Masta 1.0 through the GET parameter filter_list. The source bundle states WordPress admin authentication is required. No CVSS score, CWE, fixed version, or vendor mitigation is provided in the supplied sources.
Likely exposure
Exposure is likely limited to WordPress sites with Mail Masta 1.0 installed and reachable by authenticated WordPress admin users. Sites not using this plugin are not indicated as affected by the sources.
Exploitation context
A public Exploit-DB reference exists, but the source bundle does not show CISA KEV listing or active exploitation. Because admin authentication is required, practical risk depends on admin account security and whether the plugin remains installed.
Researcher notes
Evidence is sparse: the bundle names the vulnerable file, parameter, version, authentication requirement, and public exploit reference, but does not provide CVSS, CWE, patch status, or confirmed exploitation. Avoid assuming broader plugin versions are affected.
Mitigation direction
- Inventory WordPress sites for the Mail Masta plugin and version 1.0.
- Check vendor, WPVulnDB, or maintainer guidance for fixed versions or retirement status.
- Disable or remove the plugin where it is not required.
- Restrict WordPress admin access to trusted users and managed networks.
- Review admin account hygiene, MFA, and password reset needs.
Validation and detection
- Confirm whether Mail Masta 1.0 is installed on each WordPress site.
- Verify whether /inc/lists/view-list.php exists in the deployed plugin.
- Review web and admin logs for access to view-list.php with filter_list.
- Check for unexpected WordPress admin accounts or recent privilege changes.
- Assess database integrity if suspicious admin activity is found.
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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-6096 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/8740CVE reference · x_refsource_MISC
- https://github.com/hamkovic/Mail-Masta-Wordpress-PluginCVE reference · x_refsource_MISC
- 41438CVE reference · exploit, x_refsource_EXPLOIT-DB
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.