Skip to main content
Mallory
UnratedPublic exploitVulnerability

CVE-2025-48932: SQL Injection in Invision Community Calendar (CVE-2025-48932)

Updated 8 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2025-48932CWE-89

CVE-2025-48932 is a critical SQL Injection vulnerability in Invision Community versions up to 4.7.20, specifically within the calendar application's view.php script. The vulnerability arises from improper sanitization of the 'location' parameter in the search() method, allowing remote, unauthenticated attackers to inject arbitrary SQL queries. Exploitation requires the calendar application and a configured GeoLocation feature (such as Google Maps). The vulnerability can be leveraged to read sensitive database data, and in versions prior to 4.7.18, may enable admin account takeover or remote code execution via password reset mechanisms.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote, unauthenticated attackers to extract sensitive data from the database. In versions before 4.7.18, attackers may escalate to admin account takeover or achieve remote code execution via password reset attacks. The attack vector is particularly severe due to the unauthenticated nature and the potential for full compromise of the application and underlying server.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, disable the calendar application or the GeoLocation feature to reduce exposure. Restrict access to the affected view.php script via web server configuration. Monitor for suspicious activity and review logs for exploitation attempts. Apply virtual patching or web application firewall (WAF) rules to block malicious input in the 'location' parameter until a full upgrade can be performed.

Remediation

Patch, then assume compromise.

Upgrade Invision Community to version 4.7.21 or later, which fully patches the vulnerability. Ensure that all instances of the calendar application are updated, and verify that the GeoLocation feature is properly secured. For versions 4.7.18 and later, a new security encryption key mitigates the password reset attack vector, but upgrading to 4.7.21 is required for complete remediation.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2025-48932---exploitThis repository is a professional, production-ready Python exploit for CVE-2025-48932, a SQL injection vulnerability in Invision Community <= 4.7.20. The main exploit script (invision-sqli-exploit.py) implements a boolean-based blind SQL injection attack against the 'location' parameter in the calendar module, using a binary search algorithm to efficiently extract sensitive data such as the admin email and password reset validation key. The exploit then automates the password reset process, resulting in admin account takeover. The code is modular, object-oriented, and includes comprehensive documentation, usage examples, and CI/CD configuration. Example scripts demonstrate batch testing, custom queries, and proxy support. The exploit is operational, requiring only Python 3.7+, and is intended for educational and authorized security testing only. The main attack vector is network-based, targeting web endpoints via HTTP POST requests. The repository is well-structured, with clear separation between code, documentation, and examples.XploitGh0st · Disclosed Nov 14, 2025 · python · networkOperationalCVE-2025-48932-Invision-Community-SQLi-ExploitRepository is a standalone Python exploit project for CVE-2025-48932 targeting Invision Community blind unauthenticated SQL injection. Structure is simple: exploit.py is the main entry point and contains the exploitation logic and CLI; README.md documents capabilities, usage, and sample output; setup.sh provides optional setup and wordlist download; pyproject.toml and requirements.txt package the tool. The exploit uses a requests.Session with browser-like headers, optional HTTP/HTTPS proxying, configurable threading, and JSON result storage. A hardcoded vulnerable path (/applications/calendar/modules/front/calendar/view.php) is used to assess reachability and likely deliver SQLi probes. Based on the visible code and documentation, the main capabilities are vulnerability checking, blind SQLi-based enumeration of database metadata and contents, extraction of credentials/sessions/admin information, optional password cracking with a local wordlist, and report generation. It is not merely a detector; it is intended as an end-to-end exploitation utility. The README claims session hijacking, admin takeover, and eventual RCE via compromised admin access, but the visible code excerpt most clearly supports SQLi extraction and post-extraction credential handling rather than a fully shown direct RCE payload.CerberusMrXi · Disclosed Aug 2, 2026 · python · bash · webOperational
FAQ

Frequently asked questions

Is CVE-2025-48932 exploited in the wild?
As of Mar 19, 2026, Mallory has no reports of CVE-2025-48932 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-48932?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-48932, the earliest disclosed Nov 14, 2025.
Is there a patch for CVE-2025-48932?
Upgrade Invision Community to version 4.7.21 or later, which fully patches the vulnerability. Ensure that all instances of the calendar application are updated, and verify that the GeoLocation feature is properly secured.
Activity feed

Recent activity

6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.