CVE-2013-0735
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple SQL injection vulnerabilities in wpf.class.php in the Mingle Forum plugin before 1.0.34 for WordPress allow remote attackers to execute arbitrary SQL commands via the id parameter in a viewtopic (1) remove_post, (2) sticky, or (3) closed action or (4) thread parameter in a postreply action to index.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Mingle Forum WordPress plugin before version 1.0.34 contains multiple SQL injection vulnerabilities in wpf.class.php. The id parameter in viewtopic actions (remove_post, sticky, closed) and the thread parameter in postreply action are not properly sanitized before being used in SQL queries, allowing remote unauthenticated attackers to execute arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.33= 1.0.00= 1.0.01= 1.0.02= 1.0.03= 1.0.04= 1.0.05= 1.0.06= 1.0.07= 1.0.08= 1.0.09= 1.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Mingle Forum plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named mingle-forum, mingles-forum, or similar Mingle Forum plugin directory. Also check wp-content/plugins/mingle-forum/ for the presence of wpf.class.php.Affected if The plugin directory and wpf.class.php file exist in the WordPress installation.
-
Determine the installed plugin versionOpen the plugin's main PHP file (usually index.php or the primary plugin file in the mingle-forum directory) and look for a version comment or constant. Alternatively, check the readme.txt file in the plugin directory for the 'Stable tag' or version entry.Affected if The version is 1.0.33 or lower, or any version from 1.0.00 through 1.0.10 as listed in the affected versions.
-
Verify the vulnerable code file existsConfirm the file wpf.class.php exists in the plugin directory. This file contains the vulnerable SQL query code for the viewtopic and postreply actions.Affected if The file wpf.class.php exists in the plugin directory.
-
Check if vulnerable actions are publicly accessibleExamine the wpf.class.php file to confirm that the viewtopic action handler processes the 'id' parameter and the postreply action handler processes the 'thread' parameter without proper sanitization, and that these actions are reachable without authentication.Affected if The code shows the id or thread parameters are used directly in SQL queries without sanitization and the actions are accessible to unauthenticated users.
If the Mingle Forum plugin is installed with version 1.0.33 or lower, the vulnerable wpf.class.php file is present, and the viewtopic or postreply actions are accessible without authentication, the environment is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Mingle Forum plugin to version 1.0.34 or later to obtain the patched version that properly sanitizes user-supplied input in SQL queries.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0735 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data