LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25023: WordPress Run Contests, Raffles, and Giveaways with ContestsWP plugin <= 2.0.7 - Sensitive Data Exposure vulnerability

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in mdedev Run Contests, Raffles, and Giveaways with ContestsWP contest-code-checker allows Retrieve Embedded Sensitive Data.This issue affects Run Contests, Raffles, and Giveaways with ContestsWP: from n/a through <= 2.0.7.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25023 affects the WordPress ContestsWP contest-code-checker plugin through version 2.0.7. It may expose sensitive system information to unauthenticated outsiders. The published severity is medium because the known impact is limited to confidentiality, not site takeover or service disruption.

Executive priority

Treat as a near-term WordPress hygiene item, especially for public marketing or campaign sites using contest functionality. It is not currently supported as an emergency exploitation event, but exposed sensitive information can aid follow-on attacks.

Technical view

The issue is CWE-497: exposure of sensitive system information to an unauthorized control sphere. CVSS 3.1 is 5.3, with network attack vector, low complexity, no privileges, and no user interaction. Documented impact is low confidentiality loss only; integrity and availability are not impacted in the CVSS vector.

Likely exposure

WordPress sites using Run Contests, Raffles, and Giveaways with ContestsWP, package contest-code-checker, through version 2.0.7 are potentially exposed. Sites not running this plugin are not indicated as affected by the provided sources.

Exploitation context

The CVE record indicates unauthenticated remote exposure is possible. The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. No public exploit details are included in the provided sources.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack database reference. The provided sources do not name a patched version, workaround, exploit, or specific exposed data. Avoid assuming broader WordPress impact beyond the named plugin and versions through 2.0.7.

Mitigation direction

  • Identify whether the contest-code-checker / ContestsWP plugin is installed.
  • If installed and not business-critical, deactivate or remove it.
  • Check Patchstack and vendor guidance for a fixed version or official workaround.
  • Update only to a vendor-confirmed fixed release when available.
  • Limit public exposure of affected WordPress sites where operationally feasible.

Validation and detection

  • Inventory WordPress plugins across production and staging sites.
  • Confirm whether ContestsWP contest-code-checker is present.
  • Record the installed plugin version and flag versions through 2.0.7.
  • Review web server logs for unusual access to plugin-related paths.
  • Track Patchstack or CVE updates for remediation status changes.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-497: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2026-25023 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-25023Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mdedevRun Contests, Raffles, and Giveaways with ContestsWPcontest-code-checker, 0unaffected
Weakness

CWE details

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