Skip to main content
VulnerabilityPublished Updated

CVE-2025-10042: Quiz Maker (WordPress plugin) · SQL Injection

Affects Quiz Maker (WordPress plugin)Source CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 17 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Wordfence

    , 12 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 8 hours after disclosure

  4. First Exploit-DB entry (opens in a new tab)

    WordPress Quiz Maker 6.7.0.56 - SQL Injection

    , 99 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ays-pro Quiz MakerAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is available, administrators should consider disabling IP-based user limiting or avoid relying on user-supplied IP headers such as X-Forwarded-For for security decisions. Applying strict input validation or using a web application firewall to block suspicious header manipulations may reduce risk. Monitor vendor channels for updates and apply patches promptly once released.

Description

The Quiz Maker plugin for WordPress is vulnerable to SQL Injection via spoofed IP headers in all versions up to, and including, 6.7.0.56 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable in configurations where the server is set up to retrieve the IP from a user-supplied field like `X-Forwarded-For` and limit users by IP is enabled.

References

Community reviews

Loading reviews…