JoomlaCMS
CVE-2007-0387
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 · uneditedSQL injection vulnerability in models/category.php in the Weblinks component for Joomla! SVN 20070118 (com_weblinks) allows remote attackers to execute arbitrary SQL commands via the catid 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 in models/category.php of the Joomla! Weblinks component (com_weblinks) allows remote attackers to execute arbitrary SQL commands via the catid parameter in SVN version 20070118.
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
JoomlaCMS
= 2007-01-18CVSS 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.
-
Identify Joomla installationLocate the Joomla installation directory and check for the presence of configuration.php or index.php files typically found in Joomla installations.Affected if Joomla is not installed on the system.
-
Check Joomla versionOpen the Joomla configuration file (configuration.php) and look for the $version variable or check the version.txt file in the root directory to determine the exact Joomla version.Affected if The installed Joomla version matches the SVN version 2007-01-18.
-
Verify weblinks component presenceNavigate to the /components/com_weblinks/ directory and confirm the existence of the models/category.php file which contains the vulnerable code.Affected if The file models/category.php exists in the com_weblinks component directory.
-
Inspect the vulnerable parameter usageExamine the models/category.php file and locate the code handling the catid parameter, typically using a database query where catid is used directly without proper sanitization or parameterized queries.Affected if The catid parameter is used in SQL queries without proper input validation or prepared statements.
-
Confirm component accessibilityDetermine if the weblinks component is enabled in the Joomla administrator panel and accessible via the front-end (typically at /index.php?option=com_weblinks).Affected if The weblinks component is enabled and publicly accessible.
A system is affected if it runs Joomla version 2007-01-18 with the com_weblinks component installed and enabled, where the catid parameter in the weblinks category functionality is processed without parameterized queries.
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 dataUpdate Joomla and the weblinks component to patched versions; if unable to update, implement strict input validation and parameterized queries on the catid parameter to remediate the SQL injection.
Fix this in Joomla
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0387 — 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-2007-0387 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