CVE-2013-2629
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 · uneditedLeed (Light Feed), possibly before 1.5 Stable, allows remote attackers to bypass authorization via vectors related to the (1) importForm, (2) importFeed, (3) addFavorite, or (4) removeFavorite actions in action.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 · moderate confidenceLeed (Light Feed) RSS reader before version 1.5 Stable contains an authorization bypass vulnerability in action.php where the importForm, importFeed, addFavorite, and removeFavorite actions fail to properly validate user permissions, allowing remote attackers to perform these actions without proper authentication.
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<= 1.4CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Leed installation directorySearch for action.php file in common web directories (such as /var/www/, /home/*/public_html, or your web root). Look for a folder named 'leed' or 'LightFeed' containing action.php.Affected if Leed is installed and action.php exists in the application directory
-
Identify installed Leed versionCheck for a version file, config file, or README that displays the version number. Common locations include a version.php file, config.php, or the main index.php in the Leed directory.Affected if Version is 1.4 or earlier, or no version file is found (indicating very old installation)
-
Verify action.php contains affected functionsOpen action.php in a text editor and search for the strings: importForm, importFeed, addFavorite, and removeFavorite. These should appear as function definitions or action handlers.Affected if All four affected functions (importForm, importFeed, addFavorite, removeFavorite) are present in action.php
-
Check authorization logic in affected functionsWithin action.php, examine the code for each of the four functions. Look for session validation, authentication checks, or permission verification at the beginning of each function (e.g., checks for $_SESSION, isLoggedIn, or similar).Affected if Any of the four functions lack proper session or authentication validation at their start, or no authorization check is found before performing the action
If Leed version is 1.4 or earlier AND action.php contains the four affected functions without proper authorization checks at their entry points, the environment is vulnerable to CVE-2013-2629.
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 dataImplement proper session validation and authorization checks for all four affected actions in action.php, or upgrade to version 1.5 or later which contains the fix.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2629 — 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-2013-2629 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