Image Source ControlWordPress extension · Imagesourcecontrol
CVE-2023-52187
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Thomas Maier Image Source Control Lite – Show Image Credits and Captions.This issue affects Image Source Control Lite – Show Image Credits and Captions: from n/a through 2.17.0.
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 confidenceA sensitive information exposure vulnerability in the Image Source Control Lite WordPress plugin (versions through 2.17.0) allows unauthorized actors to access sensitive data, likely through an insecure direct object reference or unprotected endpoint. The high CVSS score of 7.5 indicates significant potential impact from 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
Image Source ControlWordPress extension
<= 2.17.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Image Source Control Lite plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and look for 'Image Source Control' or 'Imagesourcecontrol Image Source Control' in the listAffected if Plugin is present and active in WordPress
-
Check the installed plugin versionIn Plugins list, click on the plugin to view details, or inspect the plugin header in wp-content/plugins/imagesourcecontrol/image-source-control.php for 'Version:' lineAffected if Version number is 2.17.0 or lower
-
Identify plugin entry pointLocate the main plugin file at wp-content/plugins/imagesourcecontrol/image-source-control.php to understand the plugin structure and potential endpointsAffected if Plugin file exists and contains the vulnerable code pattern for versions <= 2.17.0
-
Review access logs for anomalous requestsCheck WordPress access logs (often in /wp-content/debug.log or server access logs) for unusual GET/POST requests to image-source-control-related URLs, especially those attempting to access image metadata or source data without authenticationAffected if Logs show unauthorized access attempts to plugin endpoints or unexpected queries to image source data
User is affected if the Image Source Control Lite plugin is installed with version 2.17.0 or lower, as this version range contains the sensitive information exposure vulnerability.
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 to the latest version of Image Source Control Lite when available; otherwise disable the plugin until a patch is released. Review access logs for signs of exploitation targeting this vulnerability.
Fix this in Image Source Control
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52187 — 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-2023-52187 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