School Management SystemWordPress extension · Dasinfomedia

CVE-2024-12611

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-07
Fix available
A fix is available. Upgrade to after 93.0.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The School Management System for Wordpress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'title' parameter in all versions up to, and including, 93.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 · moderate confidence

The School Management System for WordPress plugin versions up to 93.0.0 contains a reflected XSS vulnerability in the 'title' parameter due to insufficient input sanitization and output escaping. Unauthenticated attackers can inject arbitrary JavaScript by tricking users into clicking malicious links.

MitigationUpdate the plugin to a version beyond 93.0.0 when available. If no update exists, implement proper input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the 'title' parameter.

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
School Management SystemWordPress extension
Affected:<= 93.0.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'School Management System' by Dasinfomedia. The version number is displayed under the plugin name. Alternatively, inspect the main plugin file header for the 'Version' tag.
    Affected if The displayed version is 93.0.0 or lower.
  2. Identify if the title parameter is accessible
    The vulnerability exists in the 'title' parameter. Determine if your site exposes any functionality (admin panel pages, frontend forms, or public endpoints) that accepts a 'title' parameter without authentication. Check plugin settings pages, student/school record forms, or any public-facing shortcodes.
    Affected if Any functionality on your site processes a 'title' parameter and is accessible to users.
  3. Verify lack of input sanitization
    Test by submitting a benign XSS probe (such as a non-executable string like '<img src=x onerror=0>') to any field or parameter named 'title'. Inspect the page source to see if the input is rendered without encoding or if the characters appear literally.
    Affected if The submitted value appears in the page output without proper HTML encoding (characters display as entered rather than as escaped entities).

You are affected if the Dasinfomedia School Management System plugin version is 93.0.0 or lower AND your site exposes any functionality that accepts and displays a 'title' parameter to users without sanitization.

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 93.0.0
Interim mitigation

Update the plugin to a version beyond 93.0.0 when available. If no update exists, implement proper input sanitization (sanitize_text_field) and output escaping (esc_html/esc_attr) on the 'title' parameter.

Fix this in School Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12611 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12611 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