Security readout for executives and security teams
Plain-English summary
CVE-2026-3180 affects the Contest Gallery WordPress plugin. An unauthenticated attacker may be able to extract sensitive database information through blind SQL injection in lost-password related email parameters. This is a confidentiality-focused issue, not a confirmed takeover or active-exploitation event based on the provided sources.
Executive priority
Prioritize remediation soon for any internet-facing WordPress site using this plugin. The issue can be exploited without login and may expose database data. Urgency is high, but the provided sources do not confirm active exploitation.
Technical view
The plugin insufficiently escaped and prepared SQL queries involving cgLostPasswordEmail and cgl_mail. Sources state cgLostPasswordEmail was patched in 28.1.4 and cgl_mail in 28.1.5. CVSS 3.1 is 7.5: network reachable, low complexity, no authentication, no user interaction, high confidentiality impact.
Likely exposure
WordPress sites running Contest Gallery versions up to and including 28.1.4 may be exposed. Sites on 28.1.4 appear partially fixed but still affected via cgl_mail until 28.1.5. Confirm exact installed versions across production, staging, and archived sites.
Exploitation context
The issue is unauthenticated and network-accessible, which raises urgency. The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references include vulnerability intelligence and WordPress plugin source comparisons, but no exploit-in-the-wild evidence was provided.
Researcher notes
Focus validation on version state and code paths referenced by Wordfence and WordPress Trac. The patch history is important: one parameter was addressed in 28.1.4, while cgl_mail was addressed in 28.1.5. Avoid assuming full remediation at 28.1.4.
Mitigation direction
- Update Contest Gallery to version 28.1.5 or later where available.
- If immediate update is impossible, check vendor guidance for supported temporary mitigations.
- Restrict exposure of affected WordPress sites where business operations allow.
- Back up the site and database before applying plugin updates.
- Review whether sensitive database data could have been exposed.
Validation and detection
- Inventory all WordPress sites for the Contest Gallery plugin.
- Confirm installed Contest Gallery versions, including staging and backup environments.
- Verify production runs 28.1.5 or later after remediation.
- Review web logs for unusual unauthenticated lost-password or login AJAX activity.
- Monitor Wordfence, CVE, and plugin repository references for updated guidance.
Public sources used
- CVE Program
- CVE List V5
- Wordfence vulnerability entry
- WordPress Trac affected lost-password code reference 28.1.3 line 12
- WordPress Trac affected lost-password code reference 28.1.3 line 27
- WordPress Trac cg-user-functions 28.1.4 reference
- WordPress Trac cg-user-functions 28.1.5 reference
- WordPress Trac lost-password 28.1.4 patch reference
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.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase 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-2026-3180 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/91d52a64-8dc1-4923-be0b-06800382151e?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/contest-gallery/tags/28.1.3/v10/v10-admin/users/frontend/login/ajax/users-login-check-ajax-lost-password.php#L12CVE reference
- https://plugins.trac.wordpress.org/browser/contest-gallery/tags/28.1.4/functions/general/cg-user-functions.php#L140CVE reference
- https://plugins.trac.wordpress.org/browser/contest-gallery/tags/28.1.5/functions/general/cg-user-functions.php#L140CVE reference
- https://plugins.trac.wordpress.org/browser/contest-gallery/tags/28.1.4/v10/v10-admin/users/frontend/login/ajax/users-login-check-ajax-lost-password.php#L28CVE reference
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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.