Advanced Ajax Page LoaderWordPress extension · Advanced Ajax Page Loader Project
CVE-2016-10929
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 · uneditedThe advanced-ajax-page-loader plugin before 2.7.7 for WordPress has no protection against the reading of uploaded files when not logged in.
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 confidenceThe WordPress plugin 'advanced-ajax-page-loader' versions prior to 2.7.7 lacks proper access controls, allowing unauthenticated (not logged in) users to read uploaded files on the server, leading to potential sensitive information disclosure.
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
Advanced Ajax Page LoaderWordPress extension
< 2.7.7CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Verify plugin is installedCheck if the advanced-ajax-page-loader directory exists in /wp-content/plugins/ on the WordPress serverAffected if The plugin directory exists in the plugins folder
-
Check installed plugin versionOpen the main plugin file (advanced-ajax-page-loader.php) and locate the Version header in the plugin comment block, or check readme.txt for the Stable tagAffected if The version number is less than 2.7.7 or cannot be determined (older than current)
-
Confirm plugin is activeCheck WordPress admin under Plugins > Installed Plugins, or inspect the wp_options table for the active_plugins option to see if advanced-ajax-page-loader is enabledAffected if The plugin shows as Active in WordPress
-
Check for unauthenticated file access exposureInspect the plugin code for PHP files handling file requests (such as download.php, file-loader.php, or similar) and verify if they include authentication checks (such as current_user_isLoggedIn or is_user_logged_in) before serving filesAffected if The plugin lacks authentication checks before serving uploaded files to visitors
A user is affected if the advanced-ajax-page-loader plugin is installed, active, and running a version earlier than 2.7.7 without proper authentication guards on file access endpoints.
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 data2.7.7
Update the advanced-ajax-page-loader plugin to version 2.7.7 or later to implement proper authentication checks for file access, or remove the plugin if unused.
Fix this in Advanced Ajax Page Loader
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10929 — 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-2016-10929 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