CVE-2016-0956
Public exploit available. Not confirmed exploited in the wild yet. Fixed in 2.3.8.
What to do
Find your product and version, then upgrade to the build on the right.
- Maven org.apache.sling:org.apache.sling.servlets.postAffected: < 2.3.8Upgrade to: 2.3.8Stated by: GitHub advisory
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Ask your IT provider to check whether you run Adobe Experience Manager 5.6.1, 6.0.0, or 6.1.0 with the Apache Sling Post component.
- Apply Adobe’s security update for your Experience Manager release, or upgrade
org.apache.sling:org.apache.sling.servlets.postto version 2.3.8 or later where that package is managed directly. - Until updated, limit public access to the affected system and review its web-access logs for unexpected requests to Sling Post endpoints.
mvn dependency:upgrade -Dartifact=org.apache.sling:org.apache.sling.servlets.post:2.3.8What it is
From the CVE record
The Servlets Post component 2.3.6 in Apache Sling, as used in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0, allows remote attackers to obtain sensitive information via unspecified vectors.
In plain language
Written by AI from the recordApache Sling’s Post component can expose sensitive information in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0, so affected businesses should arrange the vendor fix soon.
Remote information disclosure in Apache Sling Servlets Post 2.3.6 (CWE-200) through unspecified vectors, affecting deployments used by Adobe Experience Manager.
If you're affected
- Sensitive information exposure
- Customer data exposure
- Business content exposure
- Compliance concerns
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
3 sources with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
51% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
A public exploit existed 61 days before the patch.
- EPSS band changemoderate → highepss band change
- EPSS band changehigh → moderateepss band change
- EPSS band changemoderate → high
- EPSS band changemoderate → highepss band change
- OpenVAS check added
- Patch availablerecord updated
Affected products
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Sling, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI