FKIE_CVE-2025-4203
Vulnerability from fkie_nvd - Published: 2025-10-25 07:15 - Updated: 2026-10-08 11:10| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "wpForo Forum",
"vendor": "tomdever",
"versions": [
{
"lessThanOrEqual": "2.4.8",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"source": "security@wordfence.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "The wpForo Forum plugin for WordPress is vulnerable to error\u2010based or time-based SQL Injection via the get_members() function in all versions up to, and including, 2.4.8 due to missing integer validation on the \u0027offset\u0027 and \u0027row_count\u0027 parameters. The function blindly interpolates \u0027row_count\u0027 into a \u0027LIMIT offset,row_count\u0027 clause using esc_sql() rather than enforcing numeric values. MySQL 5.x\u2019s grammar allows a \u0027PROCEDURE ANALYSE\u0027 clause immediately after a LIMIT clause. Unauthenticated attackers controlling \u0027row_count\u0027 can append a stored\u2010procedure call, enabling error\u2010based or time\u2010based blind SQL injection that can be used to extract sensitive information from the database."
},
{
"lang": "es",
"value": "El plugin wpForo Forum para WordPress es vulnerable a inyecci\u00f3n SQL basada en errores o basada en tiempo a trav\u00e9s de la funci\u00f3n get_members() en todas las versiones hasta la 2.4.8, inclusive, debido a la falta de validaci\u00f3n de enteros en los par\u00e1metros \u0027offset\u0027 y \u0027row_count\u0027. La funci\u00f3n interpola ciegamente \u0027row_count\u0027 en una cl\u00e1usula \u0027LIMIT offset,row_count\u0027 usando esc_sql() en lugar de forzar valores num\u00e9ricos. La gram\u00e1tica de MySQL 5.x permite una cl\u00e1usula \u0027PROCEDURE ANALYSE\u0027 inmediatamente despu\u00e9s de una cl\u00e1usula LIMIT. Atacantes no autenticados que controlan \u0027row_count\u0027 pueden a\u00f1adir una llamada a procedimiento almacenado, lo que permite una inyecci\u00f3n SQL ciega basada en errores o basada en tiempo que puede usarse para extraer informaci\u00f3n sensible de la base de datos."
}
],
"id": "CVE-2025-4203",
"lastModified": "2026-10-08T11:10:00.250",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "security@wordfence.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-4203",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-10-27T15:37:16.653419Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-10-25T07:15:41.130",
"references": [
{
"source": "security@wordfence.com",
"url": "https://plugins.trac.wordpress.org/browser/wpforo/tags/2.4.5/classes/Members.php#L1557"
},
{
"source": "security@wordfence.com",
"url": "https://plugins.trac.wordpress.org/browser/wpforo/tags/2.4.9/classes/Members.php#L1557"
},
{
"source": "security@wordfence.com",
"url": "https://wordpress.org/plugins/wpforo/#developers"
},
{
"source": "security@wordfence.com",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/bc406e8a-c4eb-45c3-a53c-37644e0dabfa?source=cve"
}
],
"sourceIdentifier": "security@wordfence.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-89"
}
],
"source": "security@wordfence.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.