dbcve.org
Mingle ForumApplication · Cartpauj

CVE-2012-5328

MEDIUM · 6.5 CVSS v2.0 Published 2012-10-08
Fix available
A fix is available. Upgrade to after 1.0.32.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Multiple SQL injection vulnerabilities in the Mingle Forum plugin 1.0.32.1 and other versions before 1.0.33 for WordPress might allow remote authenticated users to execute arbitrary SQL commands via the (1) memberid or (2) groupid parameters in a removemember action or (3) id parameter to fs-admin/fs-admin.php, or (4) edit_forum_id parameter in an edit_save_forum action to fs-admin/wpf-edit-forum-group.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 confidence

SQL injection vulnerabilities in the Mingle Forum WordPress plugin versions 1.0.32.1 and before 1.0.33 allow authenticated remote users to execute arbitrary SQL commands via the memberid or groupid parameters in a removemember action, the id parameter in fs-admin/fs-admin.php, or the edit_forum_id parameter in an edit_save_forum action to fs-admin/wpf-edit-forum-group.php.

MitigationUpdate the Mingle Forum plugin to version 1.0.33 or later to patch the SQL injection vulnerabilities. If custom modifications exist, ensure the fix is re-applied after updating and verify all input parameters use parameterized queries or proper escaping.

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
Mingle ForumApplication
Affected:<= 1.0.32.1= 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.10

CVSS 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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Mingle Forum plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Cartpauj Mingle Forum; note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/mingle-forum/mingle-forum.php for the Version field.
    Affected if The installed version is 1.0.32.1 or lower, or matches any of these specific versions: 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, or 1.0.10.
  2. Confirm plugin is active
    Verify that the Mingle Forum plugin shows as "Active" in the WordPress plugins list.
    Affected if The plugin is active and the version falls within the affected range.
  3. Check for vulnerable admin scripts
    Inspect the WordPress installation for the presence of fs-admin/fs-admin.php and fs-admin/wpf-edit-forum-group.php files in the mingle-forum plugin directory.
    Affected if These files exist in the plugin directory, indicating the vulnerable code is present.
  4. Verify admin functionality is accessible
    Attempt to access the fs-admin directory or check if the WordPress user roles have access to the forum admin functions (removemember action, edit_save_forum action).
    Affected if The admin functionality is accessible to authenticated users, meaning the SQL injection entry points are available.

You are affected if the Mingle Forum plugin version is 1.0.32.1 or lower (including 1.0.00 through 1.0.10) and the plugin is active with the admin scripts present and accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.32.1
Interim mitigation

Update the Mingle Forum plugin to version 1.0.33 or later to patch the SQL injection vulnerabilities. If custom modifications exist, ensure the fix is re-applied after updating and verify all input parameters use parameterized queries or proper escaping.

Fix this in Mingle Forum Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5328 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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