CVE-2024-45265
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 · uneditedA SQL injection vulnerability in the poll component in SkySystem Arfa-CMS before 5.1.3124 allows remote attackers to execute arbitrary SQL commands via the psid parameter.
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 confidenceSQL injection vulnerability exists in the poll component of SkySystem Arfa-CMS versions prior to 5.1.3124. The psid parameter in the poll functionality does not properly sanitize user input before incorporating it into SQL queries, allowing remote attackers to inject arbitrary SQL commands. The critical CVSS score of 9.8 indicates this is exploitable without authentication and leads to complete compromise of the database.
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< 5.1.3132CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Arfa-CMS versionLocate the version identifier in the CMS installation - typically found in the admin dashboard footer, a version.php file, or the meta generator tag in page sourceAffected if The installed version is lower than 5.1.3132 (any version prior to this release is affected)
-
Confirm poll component is activeAccess the poll component through the web interface - typically found at /index.php?option=com_poll or similar poll-related routesAffected if The poll component is installed and accessible to unauthenticated users
-
Locate psid parameter exposureSubmit a request to the poll component and inspect whether the psid parameter is accepted and processed - check form submissions or URL parameters containing psidAffected if The psid parameter accepts user input without sanitization or use of parameterized queries
A user is affected if their Arfa-CMS version is below 5.1.3132 AND the poll component is enabled with the psid parameter exposed to unauthenticated access.
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.
dbcve · scoped5.1.3132
Upgrade to Arfa-CMS version 5.1.3124 or later. Until patches are applied, disable or restrict access to the poll component, and implement Web Application Firewall rules to detect and block SQL injection patterns in the psid parameter.
Arfa CMS 5.1.3132 or later
- 1. Create a full backup of the current Arfa CMS installation including database and files
- 2. Download Arfa CMS version 5.1.3132 or later from the official vendor source
- 3. Apply the upgrade following the standard Arfa CMS upgrade procedure
- 4. After upgrade, verify the poll component functions correctly and test that the psid parameter is properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45265 — 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-2024-45265 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