CVE-2025-2201
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 · uneditedBroken access control vulnerability in the IcProgress Innovación y Cualificación plugin. This vulnerability allows an attacker to obtain sensitive information about other users such as public IP addresses, messages with other users and more.
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 confidenceBroken access control vulnerability in the IcProgress plugin allows authenticated attackers to access sensitive data belonging to other users, including public IP addresses and private messages, due to insufficient authorization checks on certain endpoints or functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 IcProgress plugin installationLocate the IcProgress plugin in your CMS/plugin directory (commonly found in /wp-content/plugins/, /plugins/, or similar depending on your platform). Check for a folder named 'icprogress' or similar.Affected if The IcProgress plugin is installed and active on the system
-
Check plugin versionOpen the main plugin file (usually icprogress.php or similar) and locate the version declaration (often defined as 'Version: x.x.x' or '$version ='). Compare this version against any publicly disclosed affected versions.Affected if The installed version falls within an affected version range (if publicly disclosed)
-
Identify user-specific endpointsReview the plugin source code for endpoints or functions that return user data, looking for patterns like: get_user_data, get_user_messages, fetch_user_ip, or any AJAX/action handlers that accept user IDs as parameters.Affected if The plugin contains endpoints that accept user identifiers without verifying session ownership
-
Inspect authorization logicExamine the identified user-data endpoints in the code. Look for authorization checks such as: current_user_can, verify_nonce, check_ajax_referer, or session validation before returning data.Affected if User-specific endpoints lack proper authorization checks or only validate authentication without checking data ownership
-
Test for cross-user data exposureUsing an authenticated test account, attempt to access API endpoints or URLs that request data belonging to a different user (e.g., modify parameters referencing other user IDs). Observe if sensitive data (IPs, messages) from other accounts is returned.Affected if The system returns data belonging to other users when authenticated with a standard user account
A user is affected if the IcProgress plugin is installed and user-data endpoints lack proper authorization checks to verify that the requesting user owns the requested data.
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 user authorization checks to ensure users can only access their own data; validate session/token ownership before returning any user-specific information.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2201 — 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-2025-2201 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